Junio C Hamano 8a93f9576a rebase -i: remind that the lines are top-to-bottom
Nelson Benitez Leon opened a discussion with a patch with this in the
note:

    Hi, I was using git rebase -i for some time now and never occured to
    me I could reorder the commit lines to affect the order the commits
    are applied, learnt that recently from a git tutorial.

Nelson's patch was to stress the fact that the lines in the insn sheet can
be re-ordered in a much more verbose way.  Let's add a one-liner reminder
and also remind that the lines in the insn sheet is read from top to
bottom, unlike the "git log" output.

Discussion-triggered-by: Nelson Benitez Leon
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-03-20 13:30:30 -07:00
2012-03-15 21:54:42 -07:00
2012-01-03 13:48:00 -08:00
2012-01-31 22:24:23 -08:00
2011-12-13 22:53:08 -08:00
2011-10-21 16:04:32 -07:00
2012-01-06 12:44:07 -08:00
2012-03-07 12:12:59 -08:00
2012-01-08 15:08:03 -08:00
2012-03-07 12:12:59 -08:00
2011-05-26 16:47:15 -07:00
2011-12-16 22:33:40 -08:00
2011-08-11 12:21:07 -07:00
2011-09-19 20:46:48 -07:00
2012-03-14 15:47:45 -07:00
2012-01-08 15:07:20 -08:00
2012-03-07 12:12:59 -08:00
2011-12-19 16:06:41 -08:00
2011-12-19 16:06:41 -08:00
2012-02-05 23:53:21 -08:00
2011-08-20 22:33:57 -07:00
2012-02-28 12:23:26 +08:00
2012-01-06 12:44:07 -08: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-01-06 12:44:07 -08:00
2011-12-12 16:09:38 -08:00
2011-11-07 22:12:19 -08:00
2012-02-12 19:50:39 -08:00
2012-02-12 19:50:39 -08:00
2012-03-12 15:52:52 -07:00
2012-02-22 18:17:39 -08:00
2012-02-22 18:17:39 -08:00
2011-05-30 00:09:55 -07:00
2011-11-12 22:27:38 -08:00
2011-08-01 15:00:29 -07:00
2011-05-26 16:47:15 -07:00
2011-12-11 23:16:24 -08:00
2012-02-26 23:05:45 -08:00
2012-02-22 18:17:39 -08:00
2011-12-11 23:16:25 -08: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 (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 279 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%