delta/git.git/contrib/hooks, branch ly/mktree-using-strbuf

Use 'fast-forward' all over the place

2009-10-25T06:50:28+00:00

It's a compound word.

Signed-off-by: Felipe Contreras 
Signed-off-by: Junio C Hamano

post-receive-email: hooks.showrev: show how to include both web link and patch

2009-05-23T17:29:22+00:00

Add a comment showing how to include a web link (i.e. gitweb/cgit)
and a patch in the email that is sent for each pushed commit.

The quoting was tricky enough that it's worth documenting.  To add
two blank lines (i.e. put \n\n in the printf), you would need to
say \\\\n\\\\n, and in the end, the pair of "echo" statements seemed
better.  This is used in glibc.git repository:

  http://sources.redhat.com/git/gitweb.cgi?p=glibc.git;a=summary

push-triggered messages have been sent to this list since May 21:

  http://sourceware.org/ml/glibc-cvs/2009-q2/

Signed-off-by: Junio C Hamano

Fix contrib/hooks/post-receive-email for new duplicate branch

2009-02-11T18:38:53+00:00

In the show_new_revisions function, the original code:

  git rev-parse --not --branches | grep -v $(git rev-parse $refname) |

isn't quite right since one can create a new branch and push it
without any new commits.  In that case, two refs will have the same
sha1 but both would get filtered by the 'grep'.  In the end, we'll
show ALL the history which is not what we want.  Instead, we should
list the branches by name and remove the branch being updated and THEN
pass that list through rev-parse.

Revised as suggested by Jakub Narebski and Junio C Hamano to use
git-for-each-ref instead of git-branch.  (Thanks!)

Signed-off-by: Pat Notz 
Signed-off-by: Junio C Hamano

contrib/hooks/post-receive-email: Make revision display configurable

2008-11-04T22:43:16+00:00

Add configuration option hooks.showrev, letting the user override how
revisions will be shown in the commit email.

Signed-off-by: Pete Harlan 
Signed-off-by: Junio C Hamano

contrib/hooks/post-receive-email: Put rev display in separate function

2008-11-04T22:43:07+00:00

The display of a revision in an email-appropriate format is done in
two places with similar code.  In preparation for making that display
more complex, move it into a separate function that handles both cases.

Signed-off-by: Pete Harlan 
Signed-off-by: Junio C Hamano

Add Linux PPC support to the pre-auto-gc example hook

2008-10-14T23:50:09+00:00

Signed-off-by: Miklos Vajna 
Signed-off-by: Junio C Hamano

Add OS X support to the pre-auto-gc example hook

2008-09-30T19:27:20+00:00

Signed-off-by: Jonathan del Strother 
Acked-by: Miklos Vajna 
Signed-off-by: Shawn O. Pearce

Use dashless git commands in setgitperms.perl

2008-09-22T16:36:12+00:00

Signed-off-by: Todd Zullinger 
Signed-off-by: Junio C Hamano

Ignore no-op changes in paranoid update hook

2008-05-26T03:29:30+00:00

If the hook gets invoked with identical old and new ids there
is no change taking place.  We probably should not have been
called, but instead of failing silently allow the no-op.

Signed-off-by: Shawn O. Pearce 
Signed-off-by: Junio C Hamano

Don't load missing ACL files in paranoid update hook

2008-05-26T03:29:30+00:00

If a user or group ACL file does not exist in the current tip
revision of the acl repository we will get an error from cat-file
when we ask for that blob as it cannot be resolved.  A quick look
at the history by rev-list can tell us if there is a path there
or not.

Signed-off-by: Shawn O. Pearce 
Signed-off-by: Junio C Hamano