Jeff King 7a7a517a2f parse_opt_string_list: stop allocating new strings
The parse_opt_string_list callback is basically a thin
wrapper to string_list_append() any string options we get.
However, it calls:

  string_list_append(v, xstrdup(arg));

which duplicates the option value. This is wrong for two
reasons:

  1. If the string list has strdup_strings set, then we are
     making an extra copy, which is simply leaked.

  2. If the string list does not have strdup_strings set,
     then we pass memory ownership to the string list, but
     it does not realize this. If we later call
     string_list_clear(), which can happen if "--no-foo" is
     passed, then we will leak all of the existing entries.

Instead, we should just pass the argument straight to
string_list_append, and it can decide whether to copy or not
based on its strdup_strings flag.

It's possible that some (buggy) caller could be relying on
this extra copy (e.g., because it parses some options from
an allocated argv array and then frees the array), but it's
not likely. For one, we generally only use parse_options on
the argv given to us in main(). And two, such a caller is
broken anyway, because other option types like OPT_STRING()
do not make such a copy.  This patch brings us in line with
them.

Noticed-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2016-06-13 10:33:08 -07:00
2016-03-17 11:26:41 -07:00
2015-04-18 18:35:48 -07:00
2015-08-31 15:38:52 -07:00
2014-07-28 10:14:33 -07:00
2015-08-03 11:01:27 -07:00
2015-08-25 14:57:08 -07:00
2015-08-25 14:57:08 -07:00
2015-08-11 13:48:15 -07:00
2015-05-05 21:00:23 -07:00
2015-09-28 15:33:56 -07:00
2015-08-03 11:01:21 -07:00
2015-08-03 11:01:27 -07:00
2013-12-09 14:54:48 -08:00
2015-05-20 10:19:12 -07:00
2014-12-22 12:27:20 -08:00
2014-12-12 14:31:42 -08:00
2015-06-29 11:39:10 -07:00
2014-03-31 15:29:27 -07:00
2015-06-25 10:47:46 -07:00
2015-09-28 19:16:54 -07:00
2016-03-17 11:26:18 -07:00
2015-09-28 14:57:10 -07:00
2015-05-26 13:24:46 -07:00
2014-01-17 12:21:20 -08:00
2015-08-03 11:01:18 -07:00
2015-06-29 11:39:10 -07:00
2015-09-28 15:33:56 -07:00
2016-03-17 11:26:41 -07:00
2014-09-29 12:36:11 -07:00
2014-07-07 13:56:38 -07:00
2014-07-07 13:56:38 -07:00
2015-06-24 12:21:47 -07:00
2015-03-13 22:43:11 -07:00
2016-03-16 10:41:02 -07:00
2015-09-28 15:28:31 -07:00
2015-09-28 15:33:56 -07:00
2015-08-03 11:01:27 -07:00
2014-10-20 12:23:48 -07:00
2015-03-23 11:12:58 -07:00
2015-09-04 10:43:23 -07:00
2014-10-19 15:28:30 -07:00
2014-07-21 12:35:39 -07:00
2014-03-31 15:29:27 -07:00
2014-10-10 16:02:26 -07:00
2015-08-25 14:57:08 -07:00
2016-03-17 11:26:41 -07:00
2015-05-22 09:33:08 -07:00
2015-08-25 14:57:08 -07:00
2014-06-13 11:49:40 -07:00
2014-12-22 12:27:30 -08:00
2014-12-22 12:27:30 -08:00
2014-03-31 15:29:27 -07:00
2015-09-28 19:16:54 -07:00
2015-09-28 19:16:54 -07:00
2014-09-02 13:28:44 -07:00
2015-09-09 14:30:35 -07:00
2015-08-11 14:29:36 -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 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.

See Documentation/gittutorial.txt to get started, then see
Documentation/giteveryday.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://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.
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%