Jeff King 4a5397ca79 clear_delta_base_cache_entry: use a more descriptive name
The delta base cache entries are stored in a fixed-length
hash table. So the way to remove an entry is to "clear" the
slot in the table, and that is what this function does.

However, the name is a leaky abstraction. If we were to
change the hash table implementation, it would no longer be
about "clearing". We should name it after _what_ it does,
not _how_ it does it. I.e., something like "remove" instead
of "clear".

But that does not tell the whole story, either. The subtle
thing about this function is that it removes the entry, but
does not free the entry data. So a more descriptive name is
"detach"; we give ownership of the data buffer to the
caller, and remove any other resources.

This patch uses the name detach_delta_base_cache_entry().
We could further model this after functions like
strbuf_detach(), which pass back all of the detached
information. However, since there are so many bits of
information in the struct (the data, the size, the type),
and so few callers (only one), it's not worth that
awkwardness. The name change and a comment can make the
intent clear.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2016-08-23 14:45:29 -07:00
2016-05-10 11:19:07 -07:00
2016-08-19 15:39:33 -07:00
2016-02-22 14:51:09 -08:00
2016-07-13 11:24:10 -07:00
2016-07-25 14:13:33 -07:00
2016-08-19 15:34:16 -07:00
2016-05-09 12:29:08 -07:00
2016-02-22 14:51:09 -08:00
2016-02-22 14:50:32 -08:00
2016-02-22 14:50:32 -08:00
2016-07-19 13:22:22 -07:00
2015-10-05 12:30:19 -07:00
2016-08-12 09:47:36 -07:00
2016-05-09 12:29:08 -07:00
2016-07-11 10:31:05 -07:00
2016-02-22 14:51:09 -08:00
2016-07-19 13:22:16 -07:00
2016-08-12 09:47:37 -07:00
2016-08-19 15:34:14 -07:00
2016-08-19 15:34:14 -07:00
2016-07-20 12:11:09 -07:00
2016-07-20 12:11:09 -07:00
2016-05-09 12:29:08 -07:00
2016-07-27 14:15:51 -07:00
2015-11-20 08:02:05 -05:00
2015-11-20 08:02:05 -05:00
2016-08-12 09:47:39 -07:00
2016-07-25 14:13:32 -07:00
2016-05-09 12:29:08 -07:00
2016-05-09 12:29:08 -07:00
2016-07-19 13:22:19 -07:00
2016-07-01 12:44:57 -07:00
2016-07-01 12:44:57 -07:00
2016-08-11 14:35:42 -07:00
2016-08-19 15:39:33 -07:00
2016-07-01 15:09:10 -07:00
2016-07-19 13:22:15 -07:00
2016-06-28 11:39:02 -07:00
2016-08-08 14:48:41 -07:00
2016-07-06 13:38:06 -07:00
2016-02-22 14:51:09 -08:00
2016-07-19 13:22:16 -07:00
2016-05-17 14:38:32 -07:00
2016-08-17 14:07:47 -07:00
2016-05-17 14:38:28 -07:00
2015-11-20 08:02:05 -05:00
2016-07-29 11:05:07 -07:00
2016-07-29 11:05:07 -07:00
2015-11-20 08:02:05 -05:00
2015-11-20 08:02:05 -05:00
2016-07-29 11:05:06 -07:00
2016-08-19 15:34:16 -07:00
2016-07-28 11:26:03 -07:00
2016-07-28 11:26:03 -07:00
2016-05-09 12:29:08 -07:00
2015-09-25 08:54:54 -07:00
2016-07-25 14:13:33 -07:00
2016-07-28 11:28:32 -07:00
2016-05-23 14:54:38 -07:00
2016-04-25 15:17:15 -07:00
2016-08-12 09:47:39 -07:00
2016-08-19 15:34:16 -07:00
2016-07-14 15:50:41 -07:00
2016-05-09 12:29:08 -07:00
2016-05-06 14:45:44 -07:00
2016-07-01 15:09:10 -07:00
2014-12-22 12:27:30 -08:00
2016-07-19 13:22:16 -07:00
2016-08-05 09:28:17 -07:00
2016-07-26 11:13:44 -07:00
2016-08-11 14:35:42 -07:00
2016-07-14 15:50:41 -07:00
2016-08-11 14:35:42 -07:00
2016-02-22 10:40:35 -08:00
2016-07-28 10:34:42 -07:00

Git - fast, scalable, distributed revision control system

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.

Many Git online resources are accessible from http://git-scm.com/ including full documentation and Git related tools.

See Documentation/gittutorial.txt to get started, then see Documentation/giteveryday.txt for a useful minimum set of commands, and Documentation/git-.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).

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.

The name "git" was given by Linus Torvalds when he wrote the very first version. He described the tool as "the stupid content tracker" and the name as (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
Description
No description provided
Readme 279 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%