<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/templates/hooks--commit-msg, branch gitk-resize-error</title>
<subtitle>Fork of git SCM with my patches.</subtitle>
<id>http://git.kilabit.info/git/atom?h=gitk-resize-error</id>
<link rel='self' href='http://git.kilabit.info/git/atom?h=gitk-resize-error'/>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/'/>
<updated>2008-06-25T02:06:22Z</updated>
<entry>
<title>Ship sample hooks with .sample suffix</title>
<updated>2008-06-25T02:06:22Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2008-06-25T01:45:21Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=f98f8cbac01e0d5dbb30660d7ea70af6a1439dfd'/>
<id>urn:sha1:f98f8cbac01e0d5dbb30660d7ea70af6a1439dfd</id>
<content type='text'>
We used to mark hooks we ship as samples by making them unexecutable, but
some filesystems cannot tell what is executable and what is not.

This makes it much more explicit.  The hooks are suffixed with .sample
(but now are made executable), so enabling it is still one step operation
(instead of "chmod +x $hook", you would do "mv $hook.sample $hook") but
now they won't get accidentally enabled on systems without executable bit.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>git-commit: add a prepare-commit-msg hook</title>
<updated>2008-02-06T10:26:55Z</updated>
<author>
<name>Paolo Bonzini</name>
<email>bonzini@gnu.org</email>
</author>
<published>2008-02-05T07:04:18Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=8089c85bcba89464b9b2a32fa948ed85eb367e70'/>
<id>urn:sha1:8089c85bcba89464b9b2a32fa948ed85eb367e70</id>
<content type='text'>
The prepare-commit-msg hook is run whenever a "fresh" commit message
is prepared, just before it is shown in the editor (if it is).
Its purpose is to modify the commit message in-place.

It takes one to three parameters.  The first is the name of the file that
the commit log message.  The second is the source of the commit message,
and can be: "message" (if a -m or -F option was given); "template" (if a
-t option was given or the configuration option commit.template is set);
"merge" (if the commit is a merge or a .git/MERGE_MSG file exists);
"squash" (if a .git/SQUASH_MSG file exists); or "commit", followed by
a commit SHA1 as the third parameter (if a -c, -C or --amend option
was given).

If its exit status is non-zero, git-commit will abort.  The hook is
not suppressed by the --no-verify option, so it should not be used
as a replacement for the pre-commit hook.

The sample prepare-commit-msg comments out the `Conflicts:` part of
a merge's commit message; other examples are commented out, including
adding a Signed-off-by line at the bottom of the commit messsage,
that the user can then edit or discard altogether.

Signed-off-by: Paolo Bonzini &lt;bonzini@gnu.org&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>War on whitespace</title>
<updated>2007-06-07T07:04:01Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2007-06-07T07:04:01Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=a6080a0a44d5ead84db3dabbbc80e82df838533d'/>
<id>urn:sha1:a6080a0a44d5ead84db3dabbbc80e82df838533d</id>
<content type='text'>
This uses "git-apply --whitespace=strip" to fix whitespace errors that have
crept in to our source files over time.  There are a few files that need
to have trailing whitespaces (most notably, test vectors).  The results
still passes the test, and build result in Documentation/ area is unchanged.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>hooks/commit-msg: add example to add Signed-off-by line to message</title>
<updated>2006-12-26T20:25:34Z</updated>
<author>
<name>Andy Parkins</name>
<email>andyparkins@gmail.com</email>
</author>
<published>2006-12-21T09:24:17Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=59f3e254801648322b2d5cd073ca0cc5009aa2de'/>
<id>urn:sha1:59f3e254801648322b2d5cd073ca0cc5009aa2de</id>
<content type='text'>
After checking to see if the commit message already has the target
signed-off-by (for example in --amend commits), this patch generates a
signed off by line from the repository owner and adds it to the commit
message.

Based on Johannes Schindelin's earlier patch to perform the same
function.

Originally, this was done in the pre-commit hook but Junio pointed out
that the commit-msg hook allows the message to be edited.  This has the
aditional advantage that the commit-msg hook gets passed the name of the
message file as a parameter, so it doesn't have to figure out GIT_DIR for
itself.

Signed-off-by: Andy Parkins &lt;andyparkins@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>sample commit-msg hook: no silent exit on duplicate Signed-off-by lines</title>
<updated>2006-08-13T08:46:28Z</updated>
<author>
<name>Luben Tuikov</name>
<email>ltuikov@yahoo.com</email>
</author>
<published>2006-08-13T08:41:22Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=9a1ae9ab03abaffc977421f182997f3e735e7098'/>
<id>urn:sha1:9a1ae9ab03abaffc977421f182997f3e735e7098</id>
<content type='text'>
git-commit would silently exit if duplicate Signed-off-by
lines were found.  Users of git-commit would not know it,
unless they checked '$?'.  This patch makes git-commit
actually print out a message that nothing was commited
since duplicate Signed-off-lines were found.

Signed-off-by: Luben Tuikov &lt;ltuikov@yahoo.com&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>Fix regex pattern in commit-msg</title>
<updated>2006-08-13T08:46:28Z</updated>
<author>
<name>Luben Tuikov</name>
<email>ltuikov@yahoo.com</email>
</author>
<published>2006-08-13T07:34:37Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=e77235ea38385a127d2afc969435a56d3ff2b16d'/>
<id>urn:sha1:e77235ea38385a127d2afc969435a56d3ff2b16d</id>
<content type='text'>
Between the count and the line output, some
uniq(1) versions put a TAB character, not a space.
Make sure both are handled.

Signed-off-by: Luben Tuikov &lt;ltuikov@yahoo.com&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>Big tool rename.</title>
<updated>2005-09-08T00:45:20Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2005-09-08T00:26:23Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=215a7ad1ef790467a4cd3f0dcffbd6e5f04c38f7'/>
<id>urn:sha1:215a7ad1ef790467a4cd3f0dcffbd6e5f04c38f7</id>
<content type='text'>
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 &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>Add commit hook and make the verification customizable.</title>
<updated>2005-08-19T23:23:31Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2005-08-19T00:20:08Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=89e2c5f17b901edf28a8bb778ece3f6c18bbb721'/>
<id>urn:sha1:89e2c5f17b901edf28a8bb778ece3f6c18bbb721</id>
<content type='text'>
There are three hooks:

    - 'pre-commit' is given an opportunity to inspect what is
      being committed, before we invoke the EDITOR for the
      commit message;

    - 'commit-msg' is invoked on the commit log message after
      the user prepares it;

    - 'post-commit' is run after a successful commit is made.

The first two can interfere to stop the commit.  The last one is
for after-the-fact notification.

The earlier built-in commit checker is now moved to pre-commit.

Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
</feed>
