git/Documentation/git-push.txt, branch v1.6.4

add --porcelain option to git-push

2009-06-28T05:26:58Z

If --porcelain is used git-push will produce machine-readable output. The output status line for each ref will be tab-separated and sent to stdout instead of stderr. The full symbolic names of the refs will be given. For example $ git push --dry-run --porcelain master :foobar 2>/dev/null \ | perl -pe 's/\t/ TAB /g' = TAB refs/heads/master:refs/heads/master TAB [up to date] - TAB :refs/heads/foobar TAB [deleted] Signed-off-by: Larry D'Anna Signed-off-by: Junio C Hamano

git-push.txt: describe how to default to pushing only current branch

2009-03-17T21:15:04Z

Signed-off-by: Chris Johnsen Signed-off-by: Junio C Hamano

Docs: Expand explanation of the use of + in git push refspecs.

2009-02-25T08:49:53Z

Signed-off-by: Marc Branchaud Signed-off-by: Junio C Hamano

Documentation/git-push: --all, --mirror, --tags can not be combined

2009-02-18T18:42:33Z

While b259f09 made git-push output a better error message for 'git-push --all --tags', this commit fixes the synopsis in the documentation. Inconsistency spotted and fix suggested by Jari Aalto through http://bugs.debian.org/502567 Signed-off-by: Gerrit Pape Signed-off-by: Junio C Hamano

Documentation: rework src/dst description in git push

2009-01-26T06:26:43Z

This tries to make the description of ref matching in git push easier to read. Beauty is in the eye of the beholder, though. Signed-off-by: Anders Melchiorsen Signed-off-by: Junio C Hamano

Documentation: more git push examples

2009-01-26T06:25:44Z

Include examples of using HEAD. The order of examples introduces new concepts one by one. This pushes the example of deleting a ref to the end of the list. Signed-off-by: Junio C Hamano

Documentation: simplify refspec format description

2009-01-26T06:25:20Z

The refspec format description was a mix of regexp and BNF, making it very difficult to read. The format was also wrong: it did not show that each part of a refspec is optional in different situations. Rather than having a confusing grammar, just present the format in informal prose. Signed-off-by: Anders Melchiorsen Signed-off-by: Junio C Hamano

Documentation: avoid using undefined parameters

2009-01-18T22:29:37Z

The parameter has not been introduced, so rewrite to avoid it. Signed-off-by: Anders Melchiorsen Signed-off-by: Junio C Hamano

Documentation: mention branches rather than heads

2009-01-18T22:27:52Z

The "matching refs" semantics works only on matching branches these days. Instead of using "heads" which traditionally has been used more or less interchangeably with "refs", say "branch" explicitly here. Signed-off-by: Anders Melchiorsen Signed-off-by: Junio C Hamano

Documentation: remove a redundant elaboration

2009-01-18T22:27:03Z

The comment in parentheses is wrong, as one has to leave out both the colon and . This situation is covered by the section a few lines down: A parameter without a colon pushes the from the source repository to the destination repository under the same name. So, just remove the parentheses. Signed-off-by: Anders Melchiorsen Signed-off-by: Junio C Hamano