1
0
mirror of https://github.com/git/git.git synced 2025-04-05 01:48:40 +00:00
Nguyễn Thái Ngọc Duy d5a35c114a Copy resolve_ref() return value for longer use
resolve_ref() may return a pointer to a static buffer. Callers that
use this value longer than a couple of statements should copy the
value to avoid some hidden resolve_ref() call that may change the
static buffer's value.

The bug found by Tony Wang <wwwjfy@gmail.com> in builtin/merge.c
demonstrates this. The first call is in cmd_merge()

branch = resolve_ref("HEAD", head_sha1, 0, &flag);

Then deep in lookup_commit_or_die() a few lines after, resolve_ref()
may be called again and destroy "branch".

lookup_commit_or_die
 lookup_commit_reference
  lookup_commit_reference_gently
   parse_object
    lookup_replace_object
     do_lookup_replace_object
      prepare_replace_object
       for_each_replace_ref
        do_for_each_ref
         get_loose_refs
          get_ref_dir
           get_ref_dir
            resolve_ref

All call sites are checked and made sure that xstrdup() is called if
the value should be saved.

Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2011-12-05 16:21:06 -08:00
2011-11-12 22:14:53 -08:00
2011-10-16 03:01:44 -07:00
2011-10-18 12:00:33 -07:00
2011-11-06 21:22:22 -08:00
2011-04-27 11:36:42 -07:00
2011-03-17 15:30:49 -07:00
2011-09-27 17:00:06 -07:00
2011-09-16 21:47:47 -07:00
2011-10-21 16:04:32 -07:00
2011-10-17 21:37:14 -07:00
2011-05-09 16:29:46 -07:00
2011-07-19 09:54:51 -07:00
2011-02-27 23:29:03 -08:00
2011-10-21 16:04:32 -07:00
2010-05-07 09:34:27 -07:00
2011-10-07 15:46:14 -07:00
2011-05-26 16:47:15 -07:00
2011-08-11 12:21:07 -07:00
2011-10-05 12:36:17 -07:00
2011-09-19 20:46:48 -07:00
2011-04-28 14:11:39 -07:00
2011-11-12 22:14:53 -08:00
2011-08-20 22:33:58 -07:00
2011-07-22 14:43:21 -07:00
2011-10-17 21:37:15 -07:00
2011-11-04 09:47:18 -07:00
2011-11-08 13:37:10 -08:00
2011-08-20 22:33:57 -07:00
2011-05-19 18:23:17 -07:00
2010-08-26 09:20:03 -07:00
2011-10-18 21:59:12 -07:00
2010-10-13 19:11:26 -07:00
2011-11-01 10:02:11 -07:00
2010-04-01 23:58:30 -07:00
2011-08-22 10:07:07 -07:00
2011-08-18 14:17:12 -07:00
2011-09-28 12:46:21 -07:00
2011-10-04 13:30:38 -07:00
2011-03-22 11:43:27 -07:00
2011-10-21 16:04:36 -07:00
2011-11-08 16:37:00 -08:00
2011-10-26 16:16:29 -07:00
2011-05-30 00:09:55 -07:00
2010-05-04 15:38:58 -07:00
2011-08-01 15:00:29 -07:00
2011-05-26 16:47:15 -07:00
2011-02-21 22:51:07 -08:00
2011-02-07 15:04:42 -08:00
2010-08-14 19:35:37 -07:00
2011-03-22 11:43:27 -07:00
2011-03-22 10:16:54 -07:00
2011-03-22 10:16:54 -07:00
2011-10-10 15:56:20 -07:00
2011-10-05 12:36:20 -07:00
2011-10-17 21:37:15 -07:00
2011-05-26 13:54:18 -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. 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 809 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.2%
Python 0.8%
Other 2.1%