Junio C Hamano aa6912b081 Merge branch 'mh/ref-api-lazy-loose'
Refs API is updated to lazily read sub-hierarchies of refs/ namespace,
so that we do not have to grab everything from the filesystem when we
are only interested in listing branches, for example.

By Michael Haggerty (17) and Junio C Hamano (1)
* mh/ref-api-lazy-loose:
  refs: fix find_containing_dir() regression
  refs: read loose references lazily
  read_loose_refs(): eliminate ref_cache argument
  struct ref_dir: store a reference to the enclosing ref_cache
  search_for_subdir(): return (ref_dir *) instead of (ref_entry *)
  get_ref_dir(): add function for getting a ref_dir from a ref_entry
  read_loose_refs(): rename function from get_ref_dir()
  refs: wrap top-level ref_dirs in ref_entries
  find_containing_dir(): use strbuf in implementation of this function
  bisect: copy filename string obtained from git_path()
  do_for_each_reflog(): use a strbuf to hold logfile name
  do_for_each_reflog(): return early on error
  get_ref_dir(): take the containing directory as argument
  refs.c: extract function search_for_subdir()
  get_ref_dir(): require that the dirname argument ends in '/'
  get_ref_dir(): rename "base" parameter to "dirname"
  get_ref_dir(): use a strbuf to hold refname
  get_ref_dir(): return early if directory cannot be read
2012-05-10 10:49:08 -07:00
2012-05-02 13:53:35 -07:00
2012-05-10 10:45:47 -07:00
2012-04-02 15:06:25 -07:00
2012-03-28 08:47:23 -07:00
2012-05-02 07:46:35 +08:00
2012-05-02 13:54:58 -07:00
2012-05-03 15:13:31 -07:00
2012-05-02 13:51:35 -07:00
2012-05-02 13:51:35 -07:00
2012-05-03 15:13:31 -07:00
2012-04-25 14:51:21 -07:00
2012-04-25 14:51:21 -07:00
2012-03-26 12:03:40 -07:00
2012-03-07 12:12:59 -08:00
2012-04-20 15:49:37 -07:00
2012-04-30 16:00:08 -07:00
2012-04-24 15:24:14 -07:00
2012-05-01 21:21:46 -07:00
2012-05-03 15:13:31 -07:00
2012-04-06 10:15:11 -07:00
2012-03-07 12:12:59 -08:00
2012-05-03 15:13:31 -07:00
2012-05-03 15:13:31 -07:00
2012-03-28 08:47:23 -07:00
2012-04-09 14:59:40 -07:00
2012-04-27 09:26:38 -07:00
2012-05-03 15:13:31 -07:00
2012-05-02 13:51:13 -07:00
2012-05-10 10:49:08 -07:00
2012-04-10 15:55:55 -07:00
2012-05-07 13:24:32 -07:00
2012-05-07 13:29:16 -07:00
2012-03-07 09:07:37 -08:00
2012-04-27 09:26:38 -07:00
2012-04-27 09:26:38 -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.
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-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://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 235 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%