Linus Torvalds cf2ab916af show_object(): push path_name() call further down
In particular, pushing the "path_name()" call _into_ the show() function
would seem to allow

 - more clarity into who "owns" the name (ie now when we free the name in
   the show_object callback, it's because we generated it ourselves by
   calling path_name())

 - not calling path_name() at all, either because we don't care about the
   name in the first place, or because we are actually happy walking the
   linked list of "struct name_path *" and the last component.

Now, I didn't do that latter optimization, because it would require some
more coding, but especially looking at "builtin-pack-objects.c", we really
don't even want the whole pathname, we really would be better off with the
list of path components.

Why? We use that name for two things:
 - add_preferred_base_object(), which actually _wants_ to traverse the
   path, and now does it by looking for '/' characters!
 - for 'name_hash()', which only cares about the last 16 characters of a
   name, so again, generating the full name seems to be just unnecessary
   work.

Anyway, so I didn't look any closer at those things, but it did convince
me that the "show_object()" calling convention was crazy, and we're
actually better off doing _less_ in list-objects.c, and giving people
access to the internal data structures so that they can decide whether
they want to generate a path-name or not.

This patch does that, and then for people who did use the name (even if
they might do something more clever in the future), it just does the
straightforward "name = path_name(path, component); .. free(name);" thing.

Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2009-04-12 17:28:31 -07:00
2007-06-07 00:04:01 -07:00
2008-12-19 19:27:35 -08:00
2007-06-07 00:04:01 -07:00
2007-06-07 00:04:01 -07:00
2008-07-07 02:17:23 -07: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
2008-07-19 11:17:43 -07:00
2008-10-26 16:19:59 -07:00
2007-05-30 15:03:50 -07:00
2008-07-20 17:53:17 -07:00
2007-06-07 00:04:01 -07:00
2008-07-13 14:12:48 -07:00
2008-09-19 22:05:31 -07:00
2008-07-16 17:22:50 -07:00
2008-08-28 20:50:10 -07:00
2008-03-14 00:16:42 -07:00
2008-08-03 14:14:10 -07:00
2008-10-26 14:42:57 -07:00
2008-09-15 23:11:35 -07:00
2008-07-16 14:03:24 -07:00
2007-06-07 00:04:01 -07:00
2008-07-25 17:09:38 -07:00
2008-02-25 23:57:35 -08:00
2008-08-16 02:32:36 -07:00
2008-07-15 19:09:46 -07:00
2008-08-05 21:21:08 -07:00
2008-07-13 14:12:48 -07:00
2008-07-13 14:12:48 -07:00
2008-07-13 14:12:48 -07:00
2008-09-12 16:18:47 -07:00
2008-07-13 14:12:48 -07:00
2008-08-21 22:18:21 -07:00
2008-07-13 14:12:48 -07:00
2008-07-19 11:28:06 -07:00
2008-08-04 21:52:08 -07:00
2008-07-21 19:11:50 -07:00
2008-07-21 19:11:50 -07:00
2009-02-03 22:11:44 -08:00
2007-12-13 23:04:26 -08:00
2008-02-09 23:16:51 -08:00
2008-02-25 23:57:35 -08:00
2008-07-13 14:12:48 -07:00
2008-08-06 13:50:48 -07:00
2008-08-06 13:50:48 -07:00
2007-06-07 00:04:01 -07:00
2008-10-26 14:42:57 -07:00
2008-07-21 19:11:50 -07:00
2008-12-19 19:27:35 -08:00
2008-07-21 19:11:50 -07:00
2007-11-09 21:14:10 -08:00
2008-10-06 00:37:30 -07:00
2008-07-21 19:11:50 -07:00
2008-07-25 17:09:38 -07:00
2008-07-21 19:11:50 -07:00
2008-07-21 19:11:50 -07:00
2008-03-02 15:11:07 -08:00
2007-05-01 02:59:08 -07:00
2008-07-30 11:42:01 -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 "man git-commandname" for documentation of each command.
CVS users may also want to read Documentation/cvs-migration.txt.

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%