1
0
mirror of https://github.com/git/git.git synced 2025-04-21 15:17:32 +00:00
Junio C Hamano 2888605c64 builtin-commit: fix partial-commit support
When making a partial-commit, we need to prepare two index
files, one to be used to write out the tree to be committed
(temporary index) and the other to be used as the index file
after the commit is made.

The temporary index needs to be initialized to HEAD and then all
the named paths on the command line need to be staged on top of
the index.  For this, running add_files_to_cache() that compares
what is in the index and the paths given from the command line
is not enough -- the comparison will miss the paths that the
user previously ran "git add" to the index since the HEAD
because the index reset to the HEAD would not know about them.
The index file needs to get the same modification done when
preparing the temporary index as described above.

This implementation mimics the behaviour of the scripted
version of git-commit.  It first runs overlay_tree_on_cache(),
which was stolen from ls-files with the earlier change, to get
the list of paths that the user can potentially mean, and then
uses pathspec_match() to find which ones the user meant.  This
list of paths is used to update both the temporary and the real
index file.

Additional fixes are:

 - read the index file after pre-commit hook returns, as the
   hook can modify it to affect the contents of the commit.

 - remove the temporary index file .git/next-index-* after
   commit is done or aborted.

 - run post-commit hook with the real index file to be used
   after the commit (previously it gave the temporary commit if
   a partial commit was made).

 - resurrect the safety mechanism to refuse partial commits
   during a merge to match the scripted version.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
2007-11-22 17:05:05 -08:00
2007-06-07 00:04:01 -07:00
2007-11-11 12:10:35 -08:00
2007-11-22 17:05:02 -08:00
2007-11-21 20:11:11 -08:00
2007-11-21 00:00:56 -08:00
2007-06-07 00:04:01 -07:00
2007-06-07 00:04:01 -07:00
2007-11-15 21:23:47 -08:00
2007-11-22 17:05:02 -08:00
2007-10-19 01:18:55 -04:00
2007-05-30 15:03:50 -07:00
2007-06-07 00:04:01 -07:00
2007-11-15 21:23:47 -08:00
2007-11-01 13:47:47 -07:00
2007-11-09 01:30:07 -08:00
2007-11-14 14:26:04 -08:00
2007-09-19 03:22:30 -07:00
2007-11-09 00:21:44 -08:00
2007-11-11 15:19:24 -08:00
2007-11-06 12:23:14 -08:00
2007-11-14 03:37:18 -08:00
2007-11-22 17:05:02 -08:00
2007-11-22 16:51:18 -08:00
2007-09-26 02:27:06 -07:00
2007-09-26 02:27:06 -07:00
2007-11-16 17:05:02 -08:00
2007-06-07 00:04:01 -07:00
2007-06-07 00:04:01 -07:00
2007-11-18 15:50:16 -08:00
2007-11-18 15:50:16 -08:00
2007-06-07 00:04:01 -07:00
2007-11-16 17:05:02 -08:00
2007-11-14 14:15:40 -08:00
2007-11-16 17:05:02 -08:00
2007-11-14 03:37:18 -08:00
2007-06-13 02:02:10 -07:00
2007-11-17 21:39:37 -08:00
2007-11-17 21:39:37 -08:00
2007-11-17 21:39:37 -08:00
2007-11-17 21:39:37 -08:00
2007-11-17 21:39:37 -08:00
2007-10-26 23:17:23 -07:00
2007-11-17 21:39:37 -08:00
2007-11-17 21:39:37 -08:00
2007-11-21 02:10:03 -05:00
2007-11-22 17:05:02 -08:00
2007-09-19 03:22:30 -07:00
2007-11-22 17:05:03 -08:00
2007-11-14 14:04:19 -08:00
2007-10-02 17:35:29 -07:00
2007-10-03 04:28:24 -07:00
2007-10-26 23:27:23 -07:00
2007-06-07 00:04:01 -07:00
2007-11-22 17:05:02 -08: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
2007-06-07 00:04:01 -07:00
2007-11-02 16:27:37 -07:00
2007-11-02 16:27:37 -07:00
2007-11-11 16:54:15 -08:00
2007-11-11 16:54:15 -08:00
2007-06-07 00:04:01 -07:00
2007-06-07 00:04:01 -07:00
2007-07-02 17:12:48 -07:00
2007-10-24 21:59:50 -07:00
2007-11-15 21:16:51 -08:00
2007-11-15 21:16:51 -08:00
2007-11-09 00:17:52 -08:00
2007-11-18 16:16:37 -08:00
2007-07-11 13:52:16 -07:00
2007-10-29 12:53:54 -07:00
2007-06-07 00:04:01 -07:00
2007-11-14 14:03:50 -08:00
2007-09-18 17:42:17 -07:00
2007-05-01 02:59:08 -07:00
2007-06-07 00:04:01 -07:00
2007-08-10 11:44:23 -07:00
2007-11-15 21:23:47 -08:00
2007-06-07 00:04:01 -07:00
2007-09-19 03:22:30 -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
Git Source Code Mirror - This is a publish-only repository but pull requests can be turned into patches to the mailing list via GitGitGadget (https://gitgitgadget.github.io/). Please follow Documentation/SubmittingPatches procedure for any of your improvements.
Readme 866 MiB
Languages
C 49.9%
Shell 38.6%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%