Pat Notz e5f5050ed1 Fix contrib/hooks/post-receive-email for new duplicate branch
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 <pknotz@sandia.gov>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2009-02-11 10:38:53 -08:00
2009-01-21 22:46:52 -08:00
2008-12-17 21:56:48 -08:00
2009-02-08 22:07:53 -08:00
2009-02-11 10:20:12 -08:00
2009-02-10 21:32:10 -08:00
2008-07-19 11:25:51 -07:00
2008-06-30 22:45:50 -07:00
2008-07-19 11:17:43 -07:00
2007-05-30 15:03:50 -07:00
2008-10-21 17:58:11 -07:00
2007-06-07 00:04:01 -07:00
2009-01-28 11:33:03 -08:00
2008-08-28 20:50:10 -07:00
2008-09-10 15:00:17 -07:00
2008-12-07 15:13:02 -08:00
2008-08-03 14:14:10 -07:00
2008-10-08 08:05:43 -07:00
2009-01-28 11:33:51 -08:00
2008-09-15 23:11:35 -07:00
2008-09-25 09:39:24 -07:00
2009-02-10 21:32:10 -08:00
2009-01-25 17:13:29 -08:00
2009-01-25 17:13:29 -08:00
2009-02-10 21:32:10 -08:00
2009-01-28 11:33:03 -08:00
2009-02-10 21:32:10 -08:00
2009-01-05 13:01:01 -08:00
2008-10-10 08:39:20 -07:00
2008-10-10 08:39:20 -07:00
2009-01-17 18:30:41 -08:00
2007-06-07 00:04:01 -07:00
2008-11-02 16:36:40 -08:00
2009-01-25 17:13:11 -08:00
2009-01-25 17:13:34 -08:00
2009-02-10 21:32:10 -08:00
2009-02-10 22:26:37 -08:00
2008-11-11 14:49:50 -08:00
2008-02-25 23:57:35 -08:00
2009-02-04 13:07:02 -08:00
2009-01-17 18:30:41 -08:00
2008-08-05 21:21:08 -07:00
2008-07-13 14:12:48 -07:00
2009-02-05 19:40:35 -08:00
2008-12-03 14:27:17 -08:00
2008-07-13 14:12:48 -07:00
2009-02-07 00:51:47 -08:00
2008-09-25 08:00:28 -07:00
2009-01-17 18:30:41 -08:00
2008-09-07 23:52:16 -07:00
2009-02-05 19:40:36 -08:00
2008-12-07 15:13:02 -08:00
2008-11-23 19:23:34 -08:00
2008-07-21 19:11:50 -07:00
2008-07-21 19:11:50 -07:00
2008-10-25 12:09:31 -07:00
2009-02-10 21:32:10 -08:00
2008-07-21 19:11:50 -07:00
2009-02-10 22:26:20 -08:00
2009-02-10 22:26:20 -08:00
2009-02-07 00:51:47 -08:00
2009-01-11 13:21:57 -08:00
2009-02-10 22:26:37 -08:00
2008-07-21 19:11:50 -07:00
2009-02-11 02:00:22 -08:00
2007-11-09 21:14:10 -08:00
2009-02-10 21:30:45 -08:00
2008-07-21 19:11:50 -07:00
2008-07-21 19:11:50 -07:00
2008-07-21 19:11:50 -07:00
2008-03-02 15:11:07 -08:00
2009-01-17 18:30:41 -08:00
2007-05-01 02:59:08 -07:00
2008-10-09 11:26:17 -07:00
2009-02-10 22:26:37 -08:00
2009-01-31 17:42:26 -08:00
2008-09-29 07:30:16 -07:00
2009-01-21 23:52:16 -08:00
2009-02-04 16:30:43 -08:00
2009-02-04 16:30:43 -08:00
2009-02-10 22:26:37 -08:00

////////////////////////////////////////////////////////////////

	GIT - the stupid content tracker

////////////////////////////////////////////////////////////////

"git" can mean anything, depending on your mood.

 - random three-letter combination that is pronounceable, and not
   actually used by any common UNIX command.  The fact that it is a
   mispronunciation of "get" may or may not be relevant.
 - stupid. contemptible and despicable. simple. Take your pick from the
   dictionary of slang.
 - "global information tracker": you're in a good mood, and it actually
   works for you. Angels sing, and a light suddenly fills the room.
 - "goddamn idiotic truckload of sh*t": when it breaks

Git is a fast, scalable, distributed revision control system with an
unusually rich command set that provides both high-level operations
and full access to internals.

Git is an Open Source project covered by the GNU General Public License.
It was originally written by Linus Torvalds with help of a group of
hackers around the net. It is currently maintained by Junio C Hamano.

Please read the file INSTALL for installation instructions.
See Documentation/gittutorial.txt to get started, then see
Documentation/everyday.txt for a useful minimum set of commands,
and "man git-commandname" for documentation of each command.
CVS users may also want to read Documentation/cvs-migration.txt.

Many Git online resources are accessible from http://git.or.cz/
including full documentation and Git related tools.

The user discussion and development of Git take place on the Git
mailing list -- everyone is welcome to post bug reports, feature
requests, comments and patches to git@vger.kernel.org. To subscribe
to the list, send an email with just "subscribe git" in the body to
majordomo@vger.kernel.org. The mailing list archives are available at
http://marc.theaimsgroup.com/?l=git and other archival sites.

The messages titled "A note from the maintainer", "What's in
git.git (stable)" and "What's cooking in git.git (topics)" and
the discussion following them on the mailing list give a good
reference for project status, development direction and
remaining tasks.
Description
No description provided
Readme 1,008 MiB
Languages
C 50.4%
Shell 38.9%
Perl 4.3%
Tcl 3.1%
Python 0.8%
Other 2.3%