Jeff King b717a62762 add--interactive: ignore mode change in 'p'atch command
When a path is examined in the patch subcommand, any mode changes in
the file are given to use in the diff header by git-diff. If no hunks
are staged, then we throw out that header and do not touch the
path.  But if _any_ hunks are staged, we use the header, and the mode
is changed together with the contents.

Since the 'p'atch command should just be dealing with hunks that are
shown to the user, it makes sense to just ignore mode changes
entirely. We do squirrel away the mode, though, since the next patch
will allow users to select the mode update separately.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2008-03-27 13:54:56 -07:00
2007-06-07 00:04:01 -07:00
2007-06-07 00:04:01 -07:00
2007-06-07 00:04:01 -07:00
2008-02-29 00:00:09 -08:00
2007-05-30 15:03:50 -07:00
2007-06-07 00:04:01 -07:00
2008-02-27 13:03:50 -08:00
2008-02-27 13:03:50 -08:00
2008-03-19 01:43:02 -07:00
2008-03-26 00:10:55 -07:00
2008-03-15 00:09:33 -07:00
2007-11-09 00:21:44 -08:00
2008-03-14 00:16:42 -07:00
2008-03-14 00:16:42 -07:00
2008-02-26 00:14:22 -08:00
2008-03-02 23:59:50 -08:00
2008-01-16 15:35:35 -08:00
2008-03-26 00:10:55 -07:00
2008-03-11 21:40:47 -07:00
2008-03-01 01:51:44 -08:00
2008-03-11 22:13:44 -07:00
2008-03-15 00:09:33 -07:00
2008-02-27 13:02:57 -08:00
2008-02-16 17:59:20 -08:00
2007-06-07 00:04:01 -07:00
2007-06-07 00:04:01 -07:00
2008-02-05 00:46:49 -08:00
2008-02-27 13:02:57 -08:00
2008-03-05 10:32:01 -08:00
2008-02-25 23:57:35 -08:00
2008-03-12 21:10:00 -07:00
2008-03-12 23:47:31 -07:00
2008-03-16 01:03:16 -07:00
2008-03-15 01:10:53 -07:00
2008-03-23 00:22:29 -07:00
2006-09-27 23:59:09 -07:00
2008-02-27 15:37:57 -08:00
2008-02-05 23:31:17 -08:00
2008-03-15 00:09:33 -07:00
2008-03-15 00:09:33 -07:00
2008-03-17 00:52:19 -07:00
2007-12-13 23:04:26 -08:00
2008-02-09 23:16:51 -08:00
2008-02-25 23:57:35 -08:00
2007-06-07 00:04:01 -07:00
2007-11-02 16:27:37 -07:00
2007-11-02 16:27:37 -07:00
2008-02-17 12:47:01 -08:00
2008-03-11 22:33:51 -07:00
2008-03-11 22:33:51 -07:00
2007-06-07 00:04:01 -07:00
2007-06-07 00:04:01 -07:00
2008-03-15 00:09:33 -07:00
2008-03-08 21:29:56 -08:00
2008-03-16 01:01:57 -07:00
2008-03-26 00:10:55 -07:00
2008-02-27 12:06:41 -08:00
2007-11-09 21:14:10 -08:00
2008-03-15 00:05:40 -07:00
2008-02-25 19:57:06 -08:00
2008-03-02 15:11:07 -08:00
2007-05-01 02:59:08 -07:00
2008-03-02 15:11:07 -08:00
2007-12-09 00:55:55 -08:00
2008-02-25 23:57:35 -08:00
2008-02-27 15:37:57 -08:00
2008-03-14 00:16:42 -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/tutorial.txt to get started, then see
Documentation/everyday.txt for a useful minimum set of commands,
and "man git-commandname" for documentation of each command.
CVS users may also want to read Documentation/cvs-migration.txt.

Many Git online resources are accessible from http://git.or.cz/
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 804 MiB
Languages
C 50.4%
Shell 38.8%
Perl 4.4%
Tcl 3.1%
Python 0.8%
Other 2.3%