Michael Haggerty 423c688b85 reflog_expire(): never update a reference to null_sha1
Currently, if --updateref is specified and the very last reflog entry
is expired or deleted, the reference's value is set to 0{40}. This is
an invalid state of the repository, and breaks, for example, "git
fsck" and "git for-each-ref".

The only place we use --updateref in our own code is when dropping
stash entries. In that code, the very next step is to check if the
reflog has been made empty, and if so, delete the "refs/stash"
reference entirely. Thus that code path ultimately leaves the
repository in a valid state.

But we don't want to the repository in an invalid state even
temporarily, and we don't want to leave an invalid state if other
callers of "git reflog expire|delete --updateref" don't think to do
the extra cleanup step.

So, if "git reflog expire|delete" leaves no more entries in the
reflog, just leave the reference unchanged.

Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu>
Reviewed-by: Stefan Beller <sbeller@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-03-05 12:35:37 -08:00
2014-02-27 14:01:48 -08:00
2014-06-26 13:44:11 -07:00
2015-01-30 15:02:34 -07:00
2014-07-28 10:14:33 -07:00
2014-05-15 09:49:12 -07:00
2014-05-15 09:49:12 -07:00
2015-01-07 12:55:05 -08:00
2015-01-07 12:55:05 -08:00
2015-01-07 12:55:05 -08:00
2013-12-09 14:54:48 -08:00
2014-12-22 12:27:20 -08:00
2014-01-10 10:33:09 -08:00
2014-12-12 14:31:42 -08:00
2014-03-31 15:29:27 -07:00
2014-10-20 12:23:48 -07:00
2014-06-03 12:06:40 -07:00
2014-12-17 11:42:28 -08:00
2014-01-17 12:21:20 -08:00
2014-12-22 12:27:41 -08:00
2014-10-29 10:09:35 -07:00
2015-02-05 13:23:56 -08:00
2015-01-14 12:37:19 -08:00
2014-10-08 13:05:25 -07:00
2014-09-29 12:36:11 -07:00
2014-10-31 11:49:47 -07:00
2014-07-07 13:56:38 -07:00
2014-07-07 13:56:38 -07:00
2013-07-22 16:06:49 -07:00
2014-11-03 11:00:28 -08:00
2014-10-20 12:23:48 -07:00
2014-10-20 12:23:48 -07:00
2015-01-07 12:55:05 -08:00
2013-07-29 12:32:25 -07:00
2014-10-19 15:28:30 -07:00
2014-10-19 15:28:30 -07:00
2014-12-12 14:31:42 -08:00
2014-12-17 11:46:57 -08:00
2014-07-21 12:35:39 -07:00
2014-03-31 15:29:27 -07:00
2014-10-20 12:23:48 -07:00
2014-12-22 12:27:20 -08:00
2014-12-17 11:46:57 -08:00
2014-10-10 16:02:26 -07:00
2014-12-22 12:20:38 -08:00
2014-10-08 13:05:25 -07:00
2014-09-15 11:29:46 -07:00
2014-12-22 12:27:10 -08:00
2014-12-22 12:27:10 -08:00
2014-09-02 13:28:44 -07:00
2014-10-24 14:59:10 -07:00
2014-06-13 11:49:40 -07:00
2014-12-22 12:27:30 -08:00
2014-12-22 12:27:30 -08:00
2015-01-07 12:55:05 -08:00
2014-03-31 15:29:27 -07:00
2015-01-07 19:56:44 -08:00
2014-09-02 13:28:44 -07:00
2014-12-18 12:30:53 -08:00
2015-01-07 13:28:10 -08:00
2014-12-17 11:04:39 -08:00
2014-02-27 14:04:05 -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 version 2 (some parts of it are under different licenses,
compatible with the GPLv2). It was originally written by Linus
Torvalds with help of a group of hackers around the net.

Please read the file INSTALL for installation instructions.

See Documentation/gittutorial.txt to get started, then see
Documentation/giteveryday.txt for a useful minimum set of commands, and
Documentation/git-commandname.txt for documentation of each command.
If git has been correctly installed, then the tutorial can also be
read with "man gittutorial" or "git help tutorial", and the
documentation of each command with "man git-commandname" or "git help
commandname".

CVS users may also want to read Documentation/gitcvs-migration.txt
("man gitcvs-migration" or "git help cvs-migration" if git is
installed).

Many Git online resources are accessible from http://git-scm.com/
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 (read
Documentation/SubmittingPatches for instructions on patch submission).
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://news.gmane.org/gmane.comp.version-control.git/,
http://marc.info/?l=git and other archival sites.

The maintainer frequently sends the "What's cooking" reports that
list the current status of various development topics to the mailing
list.  The discussion following them give a good reference for
project status, development direction and remaining tasks.
Description
Git with broken hash generation to generate collisions between object IDs. Don't use this!
https://undefinedbehavior.de/posts/commit-vandalism/
Readme 217 MiB
Languages
C 50%
Shell 38.2%
Perl 5.5%
Tcl 3.5%
Python 0.9%
Other 1.7%