Jeff King cd4371208a make oneline reflog dates more consistent with multiline format
The multiline reflog format (e.g., as shown by "git log -g")
will show HEAD@{<date>} rather than HEAD@{<count>} in two
situations:

  1. If the user gave branch@{<date>} syntax to specify the
     reflog

  2. If the user gave a --date=<format> specifier

It uses the "normal" date format in case 1, and the
user-specified format in case 2.

The oneline reflog format (e.g., "git reflog show" or "git
log -g --oneline") will show the date in the same two
circumstances. However, it _always_ shows the date as a
relative date, and it always ignores the timezone.

In case 2, it seems ridiculous to trigger the date but use a
format totally different from what the user requested.

For case 1, it is arguable that the user might want to see
the relative date by default; however, the multiline version
shows the normal format.

This patch does three things:

  - refactors the "relative_date" parameter to
    show_reflog_message to be an actual date_mode enum,
    since this is how it is used (it is passed to show_date)

  - uses the passed date_mode parameter in the oneline
    format (making it consistent with the multiline format)

  - does not ignore the timezone parameter in oneline mode

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2009-03-20 00:57:27 -07:00
2009-03-18 19:23:04 -07:00
2008-12-17 21:56:48 -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
2009-03-17 18:54:31 -07:00
2009-03-11 13:47:12 -07:00
2008-08-28 20:50:10 -07:00
2009-03-14 13:36:34 -07:00
2009-03-14 13:36:34 -07:00
2009-02-13 23:46:42 -08:00
2008-08-03 14:14:10 -07:00
2009-03-14 13:36:34 -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-03-17 18:55:06 -07:00
2009-02-13 17:27:58 -08:00
2009-02-13 17:27:58 -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-03-14 13:36:34 -07: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
2009-03-17 18:54:31 -07:00
2009-03-11 13:49:56 -07:00
2008-11-02 16:36:40 -08:00
2009-03-17 18:54:31 -07:00
2009-02-10 21:32:10 -08:00
2008-02-25 23:57:35 -08:00
2009-02-26 23:06:38 -08:00
2009-03-18 19:23:04 -07:00
2008-08-05 21:21:08 -07:00
2009-02-05 19:40:35 -08:00
2008-07-13 14:12:48 -07:00
2009-03-15 13:05:05 -07:00
2008-09-25 08:00:28 -07:00
2008-09-07 23:52:16 -07:00
2009-03-07 20:52:25 -08:00
2009-03-14 13:36:34 -07:00
2008-11-23 19:23:34 -08:00
2009-03-18 19:23:04 -07:00
2008-10-25 12:09:31 -07:00
2009-03-14 13:36:34 -07:00
2009-02-10 22:26:20 -08:00
2009-03-04 00:41:49 -08:00
2009-02-14 21:27:35 -08:00
2009-02-14 21:27:35 -08: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
2008-10-09 11:26:17 -07:00
2009-02-10 22:26:37 -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
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.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
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%