<feed xmlns='http://www.w3.org/2005/Atom'>
<title>user/sven/git.git/Documentation/git-commit.txt, branch v1.5.4.4</title>
<subtitle>Git
</subtitle>
<id>https://git.stealer.net/cgit.cgi/user/sven/git.git/atom?h=v1.5.4.4</id>
<link rel='self' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/atom?h=v1.5.4.4'/>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/'/>
<updated>2008-01-07T02:41:44Z</updated>
<entry>
<title>Documentation: rename gitlink macro to linkgit</title>
<updated>2008-01-07T02:41:44Z</updated>
<author>
<name>Dan McGee</name>
<email>dpmcgee@gmail.com</email>
</author>
<published>2007-12-29T06:20:38Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=5162e69732d13dd079919a389a6ace8878aad716'/>
<id>urn:sha1:5162e69732d13dd079919a389a6ace8878aad716</id>
<content type='text'>
Between AsciiDoc 8.2.2 and 8.2.3, the following change was made to the stock
Asciidoc configuration:

@@ -149,7 +153,10 @@
 # Inline macros.
 # Backslash prefix required for escape processing.
 # (?s) re flag for line spanning.
-(?su)[\\]?(?P&lt;name&gt;\w(\w|-)*?):(?P&lt;target&gt;\S*?)(\[(?P&lt;attrlist&gt;.*?)\])=
+
+# Explicit so they can be nested.
+(?su)[\\]?(?P&lt;name&gt;(http|https|ftp|file|mailto|callto|image|link)):(?P&lt;target&gt;\S*?)(\[(?P&lt;attrlist&gt;.*?)\])=
+
 # Anchor: [[[id]]]. Bibliographic anchor.
 (?su)[\\]?\[\[\[(?P&lt;attrlist&gt;[\w][\w-]*?)\]\]\]=anchor3
 # Anchor: [[id,xreflabel]]

This default regex now matches explicit values, and unfortunately in this
case gitlink was being matched by just 'link', causing the wrong inline
macro template to be applied. By renaming the macro, we can avoid being
matched by the wrong regex.

Signed-off-by: Dan McGee &lt;dpmcgee@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Allow selection of different cleanup modes for commit messages</title>
<updated>2007-12-23T03:55:07Z</updated>
<author>
<name>Alex Riesen</name>
<email>raa.lkml@gmail.com</email>
</author>
<published>2007-12-22T18:46:24Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=5f0657374344a5d8cf5ce5a9920a08c0be422194'/>
<id>urn:sha1:5f0657374344a5d8cf5ce5a9920a08c0be422194</id>
<content type='text'>
Although we traditionally stripped away excess blank lines, trailing
whitespaces and lines that begin with "#" from the commit log message,
sometimes the message just has to be the way user wants it.

For instance, a commit message template can contain lines that begin with
"#", the message must be kept as close to its original source as possible
if you are converting from a foreign SCM, or maybe the message has a shell
script including its comments for future reference.

The cleanup modes are default, verbatim, whitespace and strip. The
default mode depends on if the message is being edited and will either
strip whitespace and comments (if editor active) or just strip the
whitespace (for where the message is given explicitely).

Signed-off-by: Alex Riesen &lt;raa.lkml@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Documentation: fix --no-verify documentation for "git commit"</title>
<updated>2007-12-09T08:55:54Z</updated>
<author>
<name>Wincent Colaiuta</name>
<email>win@wincent.com</email>
</author>
<published>2007-12-08T11:38:08Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=aa6da6cddb65c3889751d0b06a7e3d339e303b1b'/>
<id>urn:sha1:aa6da6cddb65c3889751d0b06a7e3d339e303b1b</id>
<content type='text'>
The documentation for the --no-verify switch should mention the
commit-msg hook, not just the pre-commit hook.

Signed-off-by: Wincent Colaiuta &lt;win@wincent.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>git-commit documentation: fix unfinished sentence.</title>
<updated>2007-12-03T21:35:26Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2007-12-03T21:35:26Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=17ef10d0558d9622884e5b5930cee2569e40a4e4'/>
<id>urn:sha1:17ef10d0558d9622884e5b5930cee2569e40a4e4</id>
<content type='text'>
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>git-commit --allow-empty</title>
<updated>2007-12-03T08:36:49Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2007-12-03T08:03:10Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=36863af16e91aebc87696209f4f4780cf4c4059f'/>
<id>urn:sha1:36863af16e91aebc87696209f4f4780cf4c4059f</id>
<content type='text'>
It does not usually make sense to record a commit that has the exact
same tree as its sole parent commit and that is why git-commit prevents
you from making such a mistake, but when data from foreign scm is
involved, it is a different story.  We are equipped to represent such an
(perhaps insane, perhaps by mistake, or perhaps done on purpose) empty
change, and it is better to represent it bypassing the safety valve for
native use.

This is primarily for use by foreign scm interface scripts.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>replace reference to git-rm with git-reset in git-commit doc</title>
<updated>2007-11-14T09:58:03Z</updated>
<author>
<name>Jing Xue</name>
<email>jingxue@digizenstudio.com</email>
</author>
<published>2007-11-12T04:43:00Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=97e9a2216f33d1b6cff312f9535b6cf0d0ba4f16'/>
<id>urn:sha1:97e9a2216f33d1b6cff312f9535b6cf0d0ba4f16</id>
<content type='text'>
The message in git-commit suggesting to use 'git rm --cached'
to unstage is just plain wrong. It really should mention 'git reset'.

Suggested by Jan Hudec.

Signed-off-by: Jing Xue &lt;jingxue@digizenstudio.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Documentation/git-commit.txt: correct bad list formatting.</title>
<updated>2007-08-07T06:25:10Z</updated>
<author>
<name>David Kastrup</name>
<email>dak@gnu.org</email>
</author>
<published>2007-08-06T12:56:32Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=f9935bf9312dd6681e5051fbdce03204b6458c73'/>
<id>urn:sha1:f9935bf9312dd6681e5051fbdce03204b6458c73</id>
<content type='text'>
Signed-off-by: David Kastrup &lt;dak@gnu.org&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>documentation: use the word "index" in the git-commit man page</title>
<updated>2007-08-06T05:08:54Z</updated>
<author>
<name>J. Bruce Fields</name>
<email>bfields@pig.linuxdev.us.dell.com</email>
</author>
<published>2007-08-06T04:34:02Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=a76c2acb28146f5630592f2ba738c0ebf0f3c1c4'/>
<id>urn:sha1:a76c2acb28146f5630592f2ba738c0ebf0f3c1c4</id>
<content type='text'>
As with git-add, I think previous updates to the git-commit man page did
indeed help make it more user-friendly.  But I think the banishment of
the word "index" from the description goes too far; reinstate its use,
to simplify some of the language slightly and smooth the transition to
other documentation.

Signed-off-by: J. Bruce Fields &lt;bfields@citi.umich.edu&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Document commit.template configuration variable.</title>
<updated>2007-07-26T23:57:24Z</updated>
<author>
<name>Brian Gernhardt</name>
<email>benji@silverinsanity.com</email>
</author>
<published>2007-07-26T20:34:59Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=383e45cec40a0b881e59e44e011c410218ef476a'/>
<id>urn:sha1:383e45cec40a0b881e59e44e011c410218ef476a</id>
<content type='text'>
Add it to the list in config.txt and explicitly say that the
--template option to git-commit overrides the configuration variable.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Teach git-commit about commit message templates.</title>
<updated>2007-07-25T03:46:54Z</updated>
<author>
<name>Steven Grimm</name>
<email>koreth@midwinter.com</email>
</author>
<published>2007-07-23T04:17:42Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/git.git/commit/?id=d1cc130a5eb50d5bfe1e8b76cab3d8970fd70ad1'/>
<id>urn:sha1:d1cc130a5eb50d5bfe1e8b76cab3d8970fd70ad1</id>
<content type='text'>
These are useful in organizations that enforce particular formats
for commit messages, e.g., to specify bug IDs or test plans.
Use of the template is not enforced; it is simply used as the
initial content when the editor is invoked.

Signed-off-by: Steven Grimm &lt;koreth@midwinter.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
</feed>
