1
0
mirror of https://github.com/git/git.git synced 2025-03-15 10:52:17 +00:00
Junio C Hamano e1980c9d23 refs: do not create ref_entry when searching
The search_ref_dir() function is about looking up an existing ref_entry in
a sorted array of ref_entry stored in dir->entries, but it still allocates
a new ref_entry and frees it before returning.  This is only because the
call to bsearch(3) was coded in a suboptimal way. Unlike the comparison
function given to qsort(3), the first parameter to its comparison function
does not need to point at an object that is shaped like an element in the
array.

Introduce a new comparison function that takes a counted string as the key
and an element in an array of ref_entry and give it to bsearch(), so that
we do not have to allocate a new ref_entry that we will never return to
the caller anyway.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-05-22 14:28:03 -07:00
2012-05-20 18:48:10 -07:00
2012-04-02 15:06:25 -07:00
2012-03-28 08:47:23 -07:00
2012-05-16 07:32:20 +08:00
2012-05-20 15:45:35 -07:00
2012-05-03 15:13:31 -07:00
2011-03-17 15:30:49 -07:00
2012-05-02 13:51:35 -07:00
2011-10-21 16:04:32 -07:00
2012-05-03 15:13:31 -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-01-08 15:08:03 -08:00
2012-04-20 15:49:37 -07:00
2011-09-19 20:46:48 -07:00
2012-04-24 15:24:14 -07:00
2012-05-11 11:25:28 -07:00
2012-05-03 15:13:31 -07:00
2012-04-06 10:15:11 -07:00
2012-05-03 15:13:31 -07:00
2012-05-03 15:13:31 -07:00
2011-12-19 16:06:41 -08:00
2012-03-28 08:47:23 -07:00
2012-04-09 14:59:40 -07:00
2011-08-20 22:33:57 -07:00
2011-05-19 18:23:17 -07:00
2012-05-14 11:50:40 -07:00
2012-01-06 12:44:07 -08:00
2011-08-22 10:07:07 -07:00
2011-11-06 20:31:28 -08:00
2011-12-16 22:33:40 -08:00
2012-04-27 09:26:38 -07:00
2011-12-12 16:09:38 -08:00
2011-11-07 22:12:19 -08:00
2012-05-02 13:51:13 -07:00
2012-04-10 15:55:55 -07:00
2012-05-14 11:47:20 -07:00
2012-02-22 18:17:39 -08:00
2012-02-22 18:17:39 -08:00
2011-05-30 00:09:55 -07:00
2012-05-07 13:29:16 -07:00
2011-12-11 23:16:24 -08:00
2011-03-22 10:16:54 -07:00
2011-03-22 10:16:54 -07:00
2011-12-11 23:16:25 -08:00
2012-05-20 15:45:35 -07:00
2011-10-17 21:37:15 -07:00
2012-03-07 09:07:37 -08:00
2012-05-08 04:57:42 -04: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
Git Source Code Mirror - This is a publish-only repository but pull requests can be turned into patches to the mailing list via GitGitGadget (https://gitgitgadget.github.io/). Please follow Documentation/SubmittingPatches procedure for any of your improvements.
Readme 661 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%