Martin von Zweigbergk b7099a06e8 reset --keep: only write index file once
"git reset --keep" calls reset_index_file() twice, first doing a
two-way merge to the target revision, updating the index and worktree,
and then resetting the index. After each call, we write the index
file.

In the unlikely event that the second call to reset_index_file()
fails, the index will have been merged to the target revision, but
HEAD will not be updated, leaving the user with a dirty index.

By moving the locking, writing and committing out of
reset_index_file() and into the caller, we can avoid writing the index
twice, thereby making the sure we don't end up in the half-way reset
state. As a bonus, we speed up "git reset --keep" a little on the
linux-2.6 repo (best of five, warm cache):

        Before      After
real    0m0.315s    0m0.296s
user    0m0.290s    0m0.280s
sys     0m0.020s    0m0.010s

Signed-off-by: Martin von Zweigbergk <martinvonz@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2013-01-15 09:38:07 -08:00
2013-01-09 08:26:26 -08:00
2013-01-07 18:33:35 +01:00
2012-10-25 06:42:02 -04:00
2012-10-25 06:42:02 -04:00
2012-10-29 03:08:30 -04:00
2012-10-29 03:08:30 -04:00
2013-01-05 23:42:07 -08:00
2012-10-29 03:08:30 -04:00
2013-01-05 23:41:57 -08:00
2012-08-15 11:01:55 -07:00
2012-10-29 03:08:30 -04:00
2013-01-05 23:42:07 -08:00
2012-09-11 11:36:05 -07:00
2013-01-03 10:28:33 -08:00
2012-11-28 13:52:54 -08:00
2012-09-07 11:09:04 -07:00
2012-08-21 15:27:15 -07:00
2012-08-23 21:30:51 -07:00
2013-01-02 10:56:08 -08:00
2012-12-19 14:58:59 -08:00
2012-07-25 11:08:59 -07:00
2012-05-03 15:13:31 -07:00
2013-01-05 23:41:57 -08:00
2013-01-09 08:25:59 -08:00
2012-09-11 11:23:54 -07:00
2012-10-17 22:42:40 -07:00
2012-10-29 03:08:30 -04:00
2012-08-03 12:11:07 -07:00
2013-01-05 23:41:57 -08:00
2013-01-02 10:39:37 -08:00
2013-01-02 10:56:08 -08:00
2013-01-05 23:41:37 -08:00
2013-01-05 22:47:27 -08:00
2012-09-18 14:37:46 -07:00
2012-07-22 12:55:07 -07:00
2013-01-02 10:36:59 -08:00
2013-01-02 10:36:59 -08:00
2012-09-16 21:54:47 -07:00
2013-01-02 10:40:34 -08:00
2013-01-02 10:40:34 -08: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/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
No description provided
Readme 678 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%