Jeff King 560fb6a183 remove over-eager caching in sha1_file_name
This function takes a sha1 and produces a loose object
filename. It caches the location of the object directory so
that it can fill the sha1 information directly without
allocating a new buffer (and in its original incarnation,
without calling getenv(), though these days we cache that
with the code in environment.c).

This cached base directory can become stale, however, if in
a single process git changes the location of the object
directory (e.g., by running setup_work_tree, which will
chdir to the new worktree).

In most cases this isn't a problem, because we tend to set
up the git repository location and do any chdir()s before
actually looking up any objects, so the first lookup will
cache the correct location. In the case of reset --hard,
however, we do something like:

  1. look up the commit object

  2. notice we are doing --hard, run setup_work_tree

  3. look up the tree object to reset

Step (3) fails because our cache object directory value is
bogus.

This patch simply removes the caching. We use a static
buffer instead of allocating one each time (the original
version treated the malloc'd buffer as a static, so there is
no change in calling semantics).

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2010-05-25 09:21:28 -07:00
2010-02-07 15:52:28 -08:00
2010-05-02 08:27:58 -07:00
2010-01-29 22:11:00 -08:00
2010-01-29 22:11:00 -08:00
2008-07-19 11:17:43 -07:00
2010-01-16 20:39:59 -08:00
2010-01-16 20:39:59 -08:00
2009-11-23 22:30:08 -08:00
2010-01-29 23:36:13 -08:00
2010-01-20 14:39:52 -08:00
2010-03-20 11:29:35 -07:00
2009-09-13 01:32:26 -07:00
2008-10-10 08:39:20 -07:00
2009-05-01 16:07:29 -07:00
2009-05-20 00:02:24 -07:00
2009-06-18 09:22:46 -07:00
2010-05-04 15:20:47 -07:00
2010-01-13 11:58:34 -08:00
2010-01-20 14:37:25 -08:00
2010-03-24 16:26:43 -07:00
2010-02-11 23:06:32 -08:00
2009-12-13 23:40:24 -08:00
2010-03-20 11:29:19 -07:00
2010-04-03 12:28:44 -07:00
2008-07-13 14:12:48 -07:00
2010-05-01 20:23:10 -07:00
2010-03-20 11:29:35 -07:00
2010-03-15 00:52:06 -07:00
2010-04-03 12:28:39 -07:00
2010-03-20 11:29:36 -07:00
2008-09-07 23:52:16 -07:00
2010-01-21 20:03:45 -08:00
2009-04-22 19:02:12 -07:00
2010-01-12 01:06:09 -08:00
2010-01-12 01:06:09 -08:00
2010-03-24 16:26:43 -07:00
2010-01-17 22:49:36 -08:00
2010-01-17 22:49:36 -08:00
2010-04-22 23:04:21 -07:00
2010-03-15 00:58:50 -07:00
2010-01-09 23:34:10 -08:00
2010-01-09 23:34:10 -08:00
2010-01-20 14:46:35 -08:00
2010-03-24 16:26:43 -07:00
2010-03-24 16:26:43 -07:00
2010-03-07 12:47:15 -08:00
2008-07-21 19:11:50 -07:00
2010-01-21 20:03:45 -08:00
2009-11-04 17:58:15 -08:00
2010-01-20 20:28:50 -08:00
2010-01-17 22:49:36 -08:00
2008-03-02 15:11:07 -08:00
2009-01-17 18:30:41 -08:00
2009-08-30 22:04:46 -07:00
2009-08-23 17:11:28 -07:00
2009-04-20 13:44:14 -07:00
2010-01-24 17:35:58 -08:00
2010-01-24 17:35:58 -08:00
2009-11-22 16:14:48 -08:00
2010-01-16 20:39:59 -08:00
2009-07-22 21:57:41 -07:00
2010-01-16 20:39:59 -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-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. 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 582 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%