<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/templates/hooks--pre-commit, branch v1.4.2</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v1.4.2</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v1.4.2'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2006-04-19T22:37:40Z</updated>
<entry>
<title>pre-commit hook: complain about conflict markers.</title>
<updated>2006-04-19T22:37:40Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2006-04-19T21:58:24Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=61c2bcbd11e3b66a328b3850c01592e5dc1c67bb'/>
<id>urn:sha1:61c2bcbd11e3b66a328b3850c01592e5dc1c67bb</id>
<content type='text'>
Several &lt;&lt;&lt; or === or &gt;&gt;&gt; characters at the beginning of a line
is very likely to be leftover conflict markers from a failed
automerge the user resolved incorrectly, so detect them.

As usual, this can be defeated with "git commit --no-verify" if
you really do want to have those files, just like changes that
introduce trailing whitespaces.

Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>[PATCH] pre-commit sample hook: do not barf on the initial import</title>
<updated>2006-01-29T22:52:16Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2006-01-29T22:52:16Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=d37fd03222ad6b38aa6e237f5f191238c0544850'/>
<id>urn:sha1:d37fd03222ad6b38aa6e237f5f191238c0544850</id>
<content type='text'>
The example hook barfs on the initial import.  Ideally it should
produce a diff from an empty tree, but for now let's stop at
squelching the bogus error message.  Often an initial import
involves tons of badly formatted files from foreign SCM, so not
complaining about them like this patch does might actually be a
better idea than enforcing the "Perfect Patch" format on them.

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='https://git.shady.money/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>[PATCH] Fix git-commit-script to output on stderr when -v fails</title>
<updated>2005-08-20T17:54:27Z</updated>
<author>
<name>Marco Costalba</name>
<email>mcostalba@yahoo.it</email>
</author>
<published>2005-08-20T16:02:16Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=b909a15edef8c79b2b045bd90d25e19ea58f299c'/>
<id>urn:sha1:b909a15edef8c79b2b045bd90d25e19ea58f299c</id>
<content type='text'>
When git-commit-script is called with -v option and
verify test fails result is print on stdout
instead of stderr.

[jc: The original patch from Marco updated git-commit-script that
still had the piece of code in question, which has been moved to
an example hook script on its own, so I transplanted the patch to
that new file instead.]

Signed-off-by: Marco Costalba &lt;mcostalba@yahoo.it&gt;
Signed-off-by: Junio C Hamano &lt;junkio@cox.net&gt;
</content>
</entry>
<entry>
<title>Make sample pre-commit hook output Emacs friendly.</title>
<updated>2005-08-20T08:05:12Z</updated>
<author>
<name>Junio C Hamano</name>
<email>junkio@cox.net</email>
</author>
<published>2005-08-20T08:05:12Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=b779dd5ee38d103c74e15a7c361f78f1025a0872'/>
<id>urn:sha1:b779dd5ee38d103c74e15a7c361f78f1025a0872</id>
<content type='text'>
Use the common error message format, "filename:lineno: body";
this way, problematic lines can be jumped to from the Emacs
compilation buffer by C-x `.

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='https://git.shady.money/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>
