Junio C Hamano ede63a195c Merge branch 'mh/reflife'
Define memory ownership and lifetime rules for what for-each-ref
feeds to its callbacks (in short, "you do not own it, so make a
copy if you want to keep it").

* mh/reflife: (25 commits)
  refs: document the lifetime of the args passed to each_ref_fn
  register_ref(): make a copy of the bad reference SHA-1
  exclude_existing(): set existing_refs.strdup_strings
  string_list_add_refs_by_glob(): add a comment about memory management
  string_list_add_one_ref(): rename first parameter to "refname"
  show_head_ref(): rename first parameter to "refname"
  show_head_ref(): do not shadow name of argument
  add_existing(): do not retain a reference to sha1
  do_fetch(): clean up existing_refs before exiting
  do_fetch(): reduce scope of peer_item
  object_array_entry: fix memory handling of the name field
  find_first_merges(): remove unnecessary code
  find_first_merges(): initialize merges variable using initializer
  fsck: don't put a void*-shaped peg in a char*-shaped hole
  object_array_remove_duplicates(): rewrite to reduce copying
  revision: use object_array_filter() in implementation of gc_boundary()
  object_array: add function object_array_filter()
  revision: split some overly-long lines
  cmd_diff(): make it obvious which cases are exclusive of each other
  cmd_diff(): rename local variable "list" -> "entry"
  ...
2013-06-14 08:46:14 -07:00
2013-06-14 08:46:14 -07:00
2013-06-11 13:30:20 -07:00
2012-10-17 15:55:46 -07:00
2013-05-09 13:32:54 -07:00
2013-04-04 13:03:34 -07:00
2011-03-17 15:30:49 -07:00
2012-10-25 06:42:02 -04:00
2012-10-25 06:42:02 -04:00
2012-10-29 03:08:30 -04:00
2011-10-21 16:04:32 -07:00
2013-04-12 13:54:01 -07:00
2013-06-05 14:53:07 -07:00
2013-02-26 09:16:58 -08:00
2013-04-01 08:59:37 -07:00
2013-05-29 14:23:04 -07:00
2013-02-17 15:25:52 -08:00
2012-11-28 13:52:54 -08:00
2013-03-26 13:15:24 -07:00
2013-06-10 12:34:42 -07:00
2012-04-06 10:15:11 -07:00
2013-06-11 13:30:20 -07:00
2013-05-08 15:31:54 -07:00
2011-12-19 16:06:41 -08:00
2013-04-06 18:56:46 -07:00
2013-04-19 13:31:08 -07:00
2013-04-19 13:31:08 -07:00
2013-04-11 17:39:05 -07:00
2013-04-12 12:25:08 -07:00
2011-08-20 22:33:57 -07:00
2011-05-19 18:23:17 -07:00
2010-08-26 09:20:03 -07:00
2013-06-02 16:00:44 -07:00
2013-01-20 17:06:53 -08:00
2013-06-11 13:30:20 -07:00
2013-04-03 09:18:01 -07:00
2012-01-06 12:44:07 -08:00
2010-04-01 23:58:30 -07:00
2012-09-11 11:23:54 -07:00
2012-10-17 22:42:40 -07:00
2013-06-14 08:46:14 -07:00
2011-11-06 20:31:28 -08:00
2011-12-16 22:33:40 -08:00
2012-10-29 03:08:30 -04:00
2013-05-29 14:23:04 -07:00
2012-08-03 12:11:07 -07:00
2013-04-05 12:39:38 -07:00
2011-12-12 16:09:38 -08:00
2013-02-05 16:13:32 -08:00
2013-06-11 13:31:23 -07:00
2013-06-14 08:46:14 -07:00
2013-06-10 12:34:42 -07:00
2013-05-28 09:03:00 -07:00
2013-06-14 08:46:14 -07:00
2013-06-14 08:46:14 -07:00
2013-06-11 13:31:23 -07:00
2010-05-04 15:38:58 -07:00
2013-06-14 08:46:14 -07:00
2013-06-11 13:30:20 -07:00
2011-12-11 23:16:25 -08:00
2011-10-17 21:37:15 -07: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/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-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
No description provided
Readme 582 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%