Johannes Schindelin 701825de23 add -e: do not show difference in a submodule that is merely dirty
When the HEAD of the submodule matches what is recorded in the index of
the superproject, and it has local changes or untracked files, the patch
offered by "git add -e" for editing shows a diff like this:

    diff --git a/submodule b/submodule
    <header>
    -deadbeef...
    +deadbeef...-dirty

Because applying such a patch has no effect to the index, this is a
useless noise.  Generate the patch with IGNORE_DIRTY_SUBMODULES flag to
prevent such a change from getting reported.

This patch also loses the "-dirty" suffix from the output when the HEAD of
the submodule is different from what is in the index of the superproject.
As such dirtiness expressed by the suffix does not affect the result of
the patch application at all, there is no information lost if we remove
it. The user could still run "git status" before "git add -e" if s/he
cares about the dirtiness.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-02-07 08:59:40 -08:00
2012-02-05 23:50:52 -08:00
2011-03-26 10:42:35 -07:00
2011-12-29 13:08:47 -08:00
2012-01-11 00:09:36 -08:00
2011-04-27 11:36:42 -07:00
2010-01-29 22:11:00 -08:00
2010-01-29 22:11:00 -08:00
2011-03-17 15:30:49 -07:00
2012-01-11 19:07:23 -08:00
2011-08-19 11:01:36 -07:00
2011-02-13 15:13:41 -08:00
2011-02-06 22:50:26 -08:00
2011-05-31 12:19:11 -07:00
2011-05-09 16:29:46 -07:00
2009-09-13 01:32:26 -07:00
2008-10-10 08:39:20 -07:00
2011-03-22 10:16:54 -07:00
2009-05-20 00:02:24 -07:00
2009-06-18 09:22:46 -07:00
2011-08-16 11:23:26 -07:00
2011-06-06 11:40:14 -07:00
2010-05-07 09:34:27 -07:00
2011-05-06 10:50:06 -07:00
2011-05-02 15:58:30 -07:00
2011-04-28 14:11:39 -07:00
2010-06-13 20:02:50 -07:00
2012-02-05 23:50:52 -08:00
2010-06-30 15:49:18 -07:00
2011-05-09 16:29:33 -07:00
2011-05-09 16:29:33 -07:00
2010-01-21 20:03:45 -08:00
2011-08-16 11:23:26 -07:00
2011-05-26 10:32:19 -07:00
2012-02-05 23:44:56 -08:00
2010-11-24 15:13:58 -08: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-05-31 12:19:11 -07:00
2010-01-12 01:06:09 -08:00
2010-04-01 23:58:30 -07:00
2011-08-22 10:07:07 -07:00
2011-03-22 10:16:54 -07:00
2011-05-31 12:19:11 -07:00
2011-02-07 15:15:17 -08:00
2011-03-22 11:43:27 -07:00
2012-01-10 13:11:03 -08:00
2011-05-30 00:09:55 -07:00
2011-05-31 12:19:11 -07:00
2011-08-01 16:21:55 -07:00
2011-05-23 09:58:35 -07:00
2010-05-04 15:38:58 -07:00
2010-01-21 20:03:45 -08:00
2009-11-04 17:58:15 -08:00
2011-02-21 22:51:07 -08:00
2011-02-07 15:04:42 -08:00
2009-01-17 18:30:41 -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-03-22 11:43:27 -07:00
2011-03-22 10:16:54 -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%