git/Documentation/git-rev-parse.txt, branch v1.6.3

parseopt: fix documentation for --keep-dashdash

2009-04-29T23:50:10Z

Signed-off-by: Uwe Kleine-König Signed-off-by: Junio C Hamano

rev-parse: --abbrev-ref option to shorten ref name

2009-04-13T16:42:55Z

This applies the shorten_unambiguous_ref function to the object name. Default mode is controlled by core.warnAmbiguousRefs. Else it is given as optional argument to --abbrev-ref={strict|loose}. This should be faster than 'git for-each-ref --format="%(refname:short)" ' for single refs. Signed-off-by: Bert Wesarg Signed-off-by: Junio C Hamano

Documentation: remove extra quoting/emphasis around literal texts

2009-03-17T21:16:44Z

If literal text (asciidoc `...`) can be rendered in a differently from normal text for each output format (man, HTML), then we do not need extra quotes or other wrapping around inline literal text segments. config.txt Change '`...`' to `...`. In asciidoc, the single quotes provide emphasis, literal text should be distintive enough. Change "`...`" to `...`. These double quotes do not work if present in the described config value, so drop them. git-checkout.txt Change "`...`" to `...` or `"..."`. All instances are command line argument examples. One "`-`" becomes `-`. Two others are involve curly braces, so move the double quotes inside the literal region to indicate that they might need to be quoted on the command line of certain shells (tcsh). git-merge.txt Change "`...`" to `...`. All instances are used to describe merge conflict markers. The quotes should are not important. git-rev-parse.txt Change "`...`" to `...`. All instances are around command line arguments where no in-shell quoting should be necessary. gitcli.txt Change `"..."` to `...`. All instances are around command line examples or single command arguments. They do not semanticly belong inside the literal text, and they are not needed outside it. glossary-content.txt user-manual.txt Change "`...`" to `...`. All instances were around command lines. Signed-off-by: Chris Johnsen Signed-off-by: Junio C Hamano

sha1_name: support @{-N} syntax in get_sha1()

2009-01-18T02:37:19Z

Let get_sha1() parse the @{-N} syntax, with docs and tests. Note that while @{-1}^2, @{-2}~5 and such are supported, @{-1}@{1} is currently not allowed. Signed-off-by: Thomas Rast Signed-off-by: Junio C Hamano

Documentation/git-rev-parse.txt: update for new git-describe output format

2008-07-30T07:19:22Z

Signed-off-by: Cesar Eduardo Barros Signed-off-by: Junio C Hamano

Update my e-mail address

2008-07-21T19:14:42Z

The old cox.net address is still getting mails from gitters. Signed-off-by: Junio C Hamano

Documentation: update sections on naming revisions and revision ranges

2008-07-09T06:05:27Z

Various *_HEAD pseudo refs were not documented in any central place. Especially since we may be teaching rebase and am to record ORIG_HEAD, it would be a good time to do so. While at it, reword the explanation on r1..r2 notation to reduce confusion. Signed-off-by: Junio C Hamano

Merge branch 'maint'

2008-07-07T09:11:28Z

* maint: Fix grammar in git-rev-parse(1).

Fix grammar in git-rev-parse(1).

2008-07-07T02:20:50Z

Signed-off-by: Junio C Hamano

manpages: italicize git command names (which were in teletype font)

2008-07-05T18:24:40Z

The names of git commands are not meant to be entered at the commandline; they are just names. So we render them in italics, as is usual for command names in manpages. Using doit () { perl -e 'for (<>) { s/\`(git-[^\`.]*)\`/'\''\1'\''/g; print }' } for i in git*.txt config.txt diff*.txt blame*.txt fetch*.txt i18n.txt \ merge*.txt pretty*.txt pull*.txt rev*.txt urls*.txt do doit <"$i" >"$i+" && mv "$i+" "$i" done git diff . Signed-off-by: Jonathan Nieder Signed-off-by: Junio C Hamano