Jeff King 9442710801 parse_feature_request: make it easier to see feature values
We already take care to parse key/value capabilities like
"foo=bar", but the code does not provide a good way of
actually finding out what is on the right-hand side of the
"=".

A server using "parse_feature_request" could accomplish this
with some extra parsing. You must skip past the "key"
portion manually, check for "=" versus NUL or space, and
then find the length by searching for the next space (or
NUL).  But clients can't even do that, since the
"server_supports" interface does not even return the
pointer.

Instead, let's have our parser share more information by
providing a pointer to the value and its length. The
"parse_feature_value" function returns a pointer to the
feature's value portion, along with the length of the value.
If the feature is missing, NULL is returned. If it does not
have an "=", then a zero-length value is returned.

Similarly, "server_feature_value" behaves in the same way,
but always checks the static server_feature_list variable.

We can then implement "server_supports" in terms of
"server_feature_value". We cannot implement the original
"parse_feature_request" in terms of our new function,
because it returned a pointer to the beginning of the
feature. However, no callers actually cared about the value
of the returned pointer, so we can simplify it to a boolean
just as we do for "server_supports".

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-08-13 21:52:36 -07:00
2012-04-02 15:06:25 -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-03-26 12:03:40 -07:00
2012-03-07 12:12:59 -08:00
2012-01-08 15:08:03 -08:00
2012-05-11 14:31:32 -07:00
2012-04-20 15:49:37 -07:00
2011-09-19 20:46:48 -07:00
2012-05-25 12:19:45 -07:00
2012-06-03 13:11:34 -07:00
2012-04-06 10:15:11 -07:00
2012-06-03 13:11:34 -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-05-29 13:09:13 -07:00
2011-08-20 22:33:57 -07:00
2011-05-19 18:23:17 -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-05-29 13:09:02 -07:00
2012-04-10 15:55:55 -07:00
2012-06-01 13:23:11 -07:00
2011-05-30 00:09:55 -07:00
2012-06-01 13:28:19 -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-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 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%