Jeff King 77b9b1d13a add_to_alternates_file: don't add duplicate entries
The add_to_alternates_file function blindly uses
hold_lock_file_for_append to copy the existing contents, and
then adds the new line to it. This has two minor problems:

  1. We might add duplicate entries, which are ugly and
     inefficient.

  2. We do not check that the file ends with a newline, in
     which case we would bogusly append to the final line.
     This is quite unlikely in practice, though, as we call
     this function only from git-clone, so presumably we are
     the only writers of the file (and we always add a
     newline).

Instead of using hold_lock_file_for_append, let's copy the
file line by line, which ensures all records are properly
terminated. If we see an extra line, we can simply abort the
update (there is no point in even copying the rest, as we
know that it would be identical to the original).

As a bonus, we also get rid of some calls to the
static-buffer mkpath and git_path functions.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-08-10 15:15:42 -07:00
2015-05-26 13:24:46 -07:00
2015-08-03 11:20:07 -07:00
2015-07-20 11:54:40 -06:00
2015-05-05 21:00:23 -07:00
2015-08-03 11:01:27 -07:00
2015-08-03 11:01:17 -07:00
2015-05-05 21:00:23 -07:00
2015-08-03 11:01:21 -07:00
2015-08-03 11:01:21 -07:00
2015-08-03 11:01:27 -07:00
2015-06-03 09:38:19 -07:00
2015-05-20 10:19:12 -07:00
2015-06-29 11:39:10 -07:00
2015-06-25 10:47:46 -07:00
2015-08-03 11:01:20 -07:00
2015-08-03 11:01:26 -07:00
2015-05-26 13:24:46 -07:00
2015-08-03 11:01:18 -07:00
2015-06-29 11:39:10 -07:00
2015-08-03 11:01:12 -07:00
2015-08-03 11:20:07 -07:00
2015-08-03 11:01:17 -07:00
2015-06-24 12:21:47 -07:00
2015-07-13 14:00:24 -07:00
2015-08-03 11:01:27 -07:00
2015-08-03 11:01:17 -07:00
2015-08-03 11:01:17 -07:00
2015-08-03 11:19:36 -07:00
2015-06-05 12:17:37 -07:00
2015-05-22 09:33:08 -07:00
2015-08-03 11:01:27 -07:00
2015-05-05 21:00:23 -07:00
2015-08-03 11:01:13 -07:00
2015-08-03 11:01:27 -07:00
2015-08-03 11:01:27 -07:00
2015-06-05 12:17:37 -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
No description provided
Readme 635 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%