Junio C Hamano 61dfa1bb67 "rebase --onto A...B" replays history on the merge base between A and B
This is in spirit similar to "checkout A...B".  To re-queue a new set of
patches for a series that the original author prepared to apply on 'next'
on the same base as before, you would do something like this:

    $ git checkout next^0
    $ git am -s rerolled-series.mbox
    $ git rebase --onto next...jh/notes next

The first two commands recreates commits to be rebased as the original
author intended (i.e. applies directly on top of 'next'), and the rebase
command replays that history on top of the same commit the series being
replaced was built on (which is typically much older than the tip of
'next').

Signed-off-by: Junio C Hamano <gitster@pobox.com>
2009-11-21 09:22:55 -08:00
2009-10-09 00:02:23 -07:00
2009-10-17 00:11:43 -07:00
2009-05-01 22:11:57 -07:00
2009-08-31 22:09:53 -07:00
2009-09-14 02:23:36 -07:00
2008-07-19 11:17:43 -07:00
2009-06-30 16:12:24 -07:00
2009-04-17 21:05:49 -07:00
2009-06-18 09:22:46 -07:00
2007-06-07 00:04:01 -07:00
2008-08-28 20:50:10 -07:00
2009-03-14 13:36:34 -07:00
2009-08-21 18:47:53 -07:00
2009-08-05 12:39:33 -07:00
2009-10-04 14:48:51 -07:00
2009-08-07 22:35:17 -07:00
2009-02-13 17:27:58 -08:00
2009-07-22 21:56:46 -07:00
2009-09-13 01:33:18 -07:00
2009-09-13 01:32:26 -07:00
2008-10-10 08:39:20 -07:00
2009-05-01 16:07:29 -07:00
2009-07-06 09:39:46 -07:00
2009-10-03 06:04:38 -04:00
2009-05-20 00:02:24 -07:00
2009-06-18 09:22:46 -07:00
2009-08-28 19:38:19 -07:00
2009-10-17 00:11:03 -07:00
2008-11-02 16:36:40 -08:00
2009-08-21 18:47:53 -07:00
2009-04-22 19:02:12 -07:00
2008-07-13 14:12:48 -07:00
2009-10-17 00:11:43 -07:00
2009-09-13 01:31:55 -07:00
2008-09-25 08:00:28 -07:00
2009-07-02 21:36:42 -07:00
2009-09-13 01:30:53 -07:00
2009-09-18 20:00:42 -07:00
2008-09-07 23:52:16 -07:00
2009-08-05 18:37:12 -07:00
2009-09-14 14:48:27 -07:00
2009-04-22 19:02:12 -07:00
2009-10-12 16:22:35 -07:00
2008-10-25 12:09:31 -07:00
2009-08-21 18:47:53 -07:00
2009-09-18 20:00:42 -07:00
2009-08-21 18:47:53 -07:00
2009-10-17 00:11:43 -07:00
2009-06-20 21:47:27 -07:00
2009-02-14 21:27:35 -08:00
2008-07-21 19:11:50 -07:00
2008-03-02 15:11:07 -08:00
2005-11-02 16:50:58 -08:00
2006-03-25 16:35:43 -08:00
2009-01-17 18:30:41 -08:00
2009-08-30 22:04:46 -07:00
2009-09-20 12:13:47 -07:00
2009-09-13 01:31:55 -07:00
2009-04-20 13:44:14 -07:00
2009-07-18 16:57:47 -07:00
2009-10-01 04:12:21 -04:00
2009-02-04 16:30:43 -08:00
2009-07-22 21:57:41 -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 587 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%