1
0
mirror of https://github.com/git/git.git synced 2025-04-12 11:02:43 +00:00
Charles Bailey 79bc4ef368 filter-branch: eliminate duplicate mapped parents
When multiple parents of a merge commit get mapped to the same
commit, filter-branch used to pass all instances of the parent
commit to the parent and commit filters and to "git commit-tree" or
"git_commit_non_empty_tree".

This can often happen when extracting a small project from a large
repository; merges can join history with no commits on any branch
which affect the paths being retained.  Once the intermediate
commits have been filtered out, all the immediate parents of the
merge commit can end up being mapped to the same commit - either the
original merge-base or an ancestor of it.

"git commit-tree" would display an error but write the commit with
the normalized parents in any case.  "git_commit_non_empty_tree"
would fail to notice that the commit being made was in fact a
non-merge commit and would retain it even if a further pass with
"--prune-empty" would discard the commit as empty.

Ensure that duplicate parents are pruned before the parent filter to
make "--prune-empty" idempotent, removing all empty non-merge
commits in a singe pass.

Signed-off-by: Charles Bailey <cbailey32@bloomberg.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2014-07-01 08:30:41 -07:00
2014-02-27 14:01:48 -08:00
2014-06-25 12:21:11 -07:00
2014-04-08 12:00:28 -07:00
2014-03-31 15:29:33 -07:00
2014-05-17 19:08:59 +02:00
2014-02-27 14:01:09 -08:00
2014-01-10 10:32:18 -08:00
2013-06-10 10:55:42 -07:00
2014-03-31 15:29:27 -07:00
2013-12-09 14:54:48 -08:00
2014-01-17 12:21:20 -08:00
2013-07-22 16:06:49 -07:00
2014-01-10 10:33:09 -08:00
2014-01-10 10:33:09 -08:00
2014-02-10 10:46:35 -08:00
2014-03-31 15:29:27 -07:00
2014-04-03 12:38:38 -07:00
2013-07-19 09:26:15 -07:00
2014-01-17 12:21:20 -08:00
2014-04-08 12:00:28 -07:00
2014-06-25 12:21:11 -07:00
2014-03-18 13:51:20 -07:00
2013-05-10 10:27:31 -07:00
2013-05-08 15:31:54 -07:00
2014-03-14 14:26:29 -07:00
2014-04-08 12:00:28 -07:00
2013-04-11 17:39:05 -07:00
2013-07-22 16:06:49 -07:00
2014-04-08 12:00:33 -07:00
2013-07-29 12:32:25 -07:00
2014-04-08 12:00:17 -07:00
2014-04-08 12:00:17 -07:00
2014-03-31 15:29:27 -07:00
2013-07-30 08:13:38 -07:00
2013-07-30 08:13:38 -07:00
2013-02-05 16:13:32 -08:00
2014-03-18 13:51:05 -07:00
2014-06-25 12:21:11 -07:00
2013-07-15 10:56:07 -07:00
2014-04-08 12:00:33 -07:00
2014-01-17 12:21:20 -08:00
2014-05-28 15:45:57 -07:00
2014-02-27 14:01:09 -08:00
2014-03-31 15:29:27 -07:00
2013-09-17 11:37:33 -07:00
2013-09-17 11:37:33 -07:00
2014-03-14 14:26:31 -07:00
2014-02-27 14:04:05 -08: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 version 2 (some parts of it are under different licenses,
compatible with the GPLv2). It was originally written by Linus
Torvalds with help of a group of hackers around the net.

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://news.gmane.org/gmane.comp.version-control.git/,
http://marc.info/?l=git and other archival sites.

The maintainer frequently sends the "What's cooking" reports that
list the current status of various development topics to the mailing
list.  The discussion following them 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 829 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.2%
Python 0.8%
Other 2.1%