path: root/Documentation/git-push.txt
AgeCommit message (Collapse)Author
2007-01-16git-push documentation: remaining bitsJunio C Hamano
Mention --thin, --no-thin, --repo and -v. Signed-off-by: Junio C Hamano <>
2007-01-16document --exec for git-pushUwe Kleine-K,Av(Bnig
The text is just copied from git-send-pack.txt. Signed-off-by: Uwe Kleine-K,Av(Bnig <> Signed-off-by: Junio C Hamano <>
2006-12-13git-push: document removal of remote ref with :<dst> pathspecJunio C Hamano
Signed-off-by: Junio C Hamano <>
2006-08-02git-push: allow -f as an alias for --forceJeff King
This was already documented in the options section of the manpage. This patch implements it, adds it to the usage message, and mentions it at the top of the manpage. Signed-off-by: Jeff King <> Signed-off-by: Junio C Hamano <>
2006-07-09Assorted typo fixesPavel Roskin
Signed-off-by: Junio C Hamano <>
2006-03-09Remove trailing dot after short descriptionFredrik Kuivinen
Signed-off-by: Fredrik Kuivinen <> Signed-off-by: Junio C Hamano <>
2006-02-22git-push: Update documentation to describe the no-refspec behavior.Carl Worth
It turns out that the git-push documentation didn't describe what it would do when not given a refspec, (not on the command line, nor in a remotes file). This is fairly important for the user who is trying to understand operations such as: git clone git://something/some/where # hack, hack, hack git push origin I tracked the mystery behavior down to git-send-pack and lifted the relevant portion of its documentation up to git-push, (namely that all refs existing both locally and remotely are updated). Signed-off-by: Carl Worth <> Signed-off-by: Junio C Hamano <>
2006-02-07Docs: minor git-push copyeditingJ. Bruce Fields
Minor git-push copyediting Signed-off-by: J. Bruce Fields <> Signed-off-by: Junio C Hamano <>
2006-02-07Docs: move git url and remotes text to separate sectionsJ. Bruce Fields
The sections on git urls and remotes files in the git-fetch, git-pull, and git-push manpages seem long enough to be worth a manpage section of their own. Signed-off-by: J. Bruce Fields <> Signed-off-by: Junio C Hamano <>
2006-02-07Docs: split up pull-fetch-param.txtJ. Bruce Fields
The push and pull man pages include a bunch of shared text from pull-fetch-param.txt. This simplifies maintenance somewhat, but there's actually quite a bit of text that applies only to one or the other. So, separate out the push- and pull/fetch-specific text into pull-fetch-param.txt and git-push.txt, then include the largest chunk of common stuff (the description of protocols and url's) from urls.txt. That cuts some irrelevant stuff from the man pages without making us duplicate too much. Signed-off-by: J. Bruce Fields <> Signed-off-by: Junio C Hamano <>
2006-01-30Merge fixes up to GIT 1.1.6Junio C Hamano
2006-01-30git push -f documentationJ. Bruce Fields
Signed-off-by: Junio C Hamano <>
2006-01-16git-push: fix --tags and document it.Junio C Hamano
Previously 'git-push --tags dst', used information from remotes/dst to determine which refs to push; this patch corrects it, and also documents the --tags option. Signed-off-by: Junio C Hamano <>
2005-12-05Documentation: push/receive hook references.Junio C Hamano
Mention documentation pages that talk about update and post-update hooks from git-push, because a frequently asked question is "I want X to happen when I push" and people would not know to look at git-receive-pack documentation until they understand that is what runs on the other end. Signed-off-by: Junio C Hamano <>
2005-10-20git-fetch/push/pull: documentation.Junio C Hamano
The documentation was lazily sharing the argument description across these commands. Lazy may be a way of life, but that does not justify confusing others ;-). Signed-off-by: Junio C Hamano <>
2005-09-20[PATCH] Documentation: Update all files to use the new gitlink: macroSergey Vlasov
The replacement was performed automatically by these commands: perl -pi -e 's/link:(git.+)\.html\[\1\]/gitlink:$1\[1\]/g' \ README Documentation/*.txt perl -pi -e 's/link:git\.html\[git\]/gitlink:git\[7\]/g' \ README Documentation/*.txt Signed-off-by: Sergey Vlasov <> Signed-off-by: Junio C Hamano <>
2005-09-08Big tool rename.Junio C Hamano
As promised, this is the "big tool rename" patch. The primary differences since 0.99.6 are: (1) git-*-script are no more. The commands installed do not have any such suffix so users do not have to remember if something is implemented as a shell script or not. (2) Many command names with 'cache' in them are renamed with 'index' if that is what they mean. There are backward compatibility symblic links so that you and Porcelains can keep using the old names, but the backward compatibility support is expected to be removed in the near future. Signed-off-by: Junio C Hamano <>