Jonathan Nieder 218b65fbf9 revert: do not remove state until sequence is finished
As v1.7.8-rc0~141^2~4 (2011-08-04) explains, git cherry-pick removes
the sequencer state just before applying the final patch.  In the
single-pick case, that was a good thing, since --abort and --continue
work fine without access to such state and removing it provides a
signal that git should not complain about the need to clobber it ("a
cherry-pick or revert is already in progress") in sequences like the
following:

	git cherry-pick foo
	git read-tree -m -u HEAD; # forget that; let's try a different one
	git cherry-pick bar

After the recent patch "allow single-pick in the middle of cherry-pick
sequence" we don't need that hack any more.  In the new regime, a
traditional "git cherry-pick <commit>" command never looks at
.git/sequencer, so we do not need to cripple "git cherry-pick
<commit>..<commit>" for it any more.

So now you can run "git cherry-pick --abort" near the end of a
multi-pick sequence and it will abort the entire sequence, instead of
misbehaving and aborting just the final commit.

Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2011-12-12 13:33:53 -08:00
2011-10-16 03:01:44 -07:00
2011-10-18 12:00:33 -07: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-21 16:04:32 -07:00
2011-05-09 16:29:46 -07:00
2009-09-13 01:32:26 -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
2009-05-20 00:02:24 -07:00
2009-06-18 09:22:46 -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-18 11:28:05 -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-15 16:08:48 -08:00
2011-11-08 13:37:10 -08:00
2011-08-20 22:33:57 -07:00
2009-04-22 19:02:12 -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
2011-11-18 11:14:00 -08:00
2010-01-12 01:06:09 -08:00
2010-04-01 23:58:30 -07:00
2011-11-18 11:30:02 -08: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-11-16 21:52:24 -08:00
2011-10-21 16:04:36 -07:00
2011-11-18 11:28:05 -08:00
2011-10-26 16:16:29 -07:00
2011-10-26 16:16:29 -07:00
2011-05-30 00:09:55 -07:00
2011-11-15 16:09:20 -08:00
2010-05-04 15:38:58 -07:00
2009-11-04 17:58:15 -08: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
2009-08-23 17:11:28 -07: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
No description provided
Readme 582 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%