1
0
mirror of https://github.com/git/git.git synced 2025-04-21 07:37:20 +00:00
Junio C Hamano ebdc94f3be revision: --ancestry-path
"rev-list A..H" computes the set of commits that are ancestors of H, but
excludes the ones that are ancestors of A.  This is useful to see what
happened to the history leading to H since A, in the sense that "what does
H have that did not exist in A" (e.g. when you have a choice to update to
H from A).

	       x---x---A---B---C  <-- topic
	      /			\
     x---x---x---o---o---o---o---M---D---E---F---G  <-- dev
    /						  \
   x---o---o---o---o---o---o---o---o---o---o---o---N---H  <-- master

The result in the above example would be the commits marked with caps
letters (except for A itself, of course), and the ones marked with 'o'.

When you want to find out what commits in H are contaminated with the bug
introduced by A and need fixing, however, you might want to view only the
subset of "A..B" that are actually descendants of A, i.e. excluding the
ones marked with 'o'.  Introduce a new option --ancestry-path to compute
this set with "rev-list --ancestry-path A..B".

Note that in practice, you would build a fix immediately on top of A and
"git branch --contains A" will give the names of branches that you would
need to merge the fix into (i.e. topic, dev and master), so this may not
be worth paying the extra cost of postprocessing.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
2010-04-21 01:15:33 -07:00
2010-04-19 22:41:30 -07:00
2010-04-19 22:41:30 -07:00
2010-04-06 14:50:45 -07:00
2010-04-18 22:19:04 -07:00
2010-02-07 15:52:28 -08:00
2010-04-21 01:15:33 -07:00
2010-01-29 22:11:00 -08:00
2010-01-29 22:11:00 -08:00
2010-01-16 20:39:59 -08:00
2010-01-16 20:39:59 -08:00
2009-11-23 22:30:08 -08:00
2010-01-29 23:36:13 -08:00
2010-01-20 14:39:52 -08:00
2010-03-20 11:29:35 -07:00
2009-09-13 01:32:26 -07:00
2010-01-13 11:58:34 -08:00
2010-01-20 14:37:25 -08:00
2010-03-24 16:26:43 -07:00
2010-02-11 23:06:32 -08:00
2009-12-13 23:40:24 -08:00
2010-03-20 11:29:19 -07:00
2010-04-03 12:28:44 -07:00
2010-03-20 11:29:35 -07:00
2010-04-18 22:19:04 -07:00
2010-03-15 00:52:06 -07:00
2010-04-03 12:28:39 -07:00
2010-03-20 11:29:36 -07:00
2010-01-21 20:03:45 -08:00
2010-01-12 01:06:09 -08:00
2010-01-12 01:06:09 -08:00
2010-04-10 13:02:22 -07:00
2010-03-24 16:26:43 -07:00
2010-01-17 22:49:36 -08:00
2010-01-17 22:49:36 -08:00
2010-04-11 13:42:33 -07:00
2010-03-15 00:58:50 -07:00
2010-01-09 23:34:10 -08:00
2010-01-09 23:34:10 -08:00
2010-01-20 14:46:35 -08:00
2010-04-21 01:15:33 -07:00
2010-04-21 01:15:33 -07:00
2010-03-07 12:47:15 -08:00
2010-01-21 20:03:45 -08:00
2009-11-04 17:58:15 -08:00
2010-01-20 20:28:50 -08:00
2010-01-17 22:49:36 -08:00
2009-08-30 22:04:46 -07:00
2009-08-23 17:11:28 -07:00
2010-01-24 17:35:58 -08:00
2010-01-24 17:35:58 -08:00
2009-11-22 16:14:48 -08:00
2010-01-16 20:39:59 -08:00
2010-01-16 20:39:59 -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.
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
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%