Git development
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Brian Foster <brian.foster@innova-card.com>,
	Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [Q] Abbreviated history graph?
Date: Mon, 3 Nov 2008 11:32:37 -0800 (PST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0811031129060.3419@nehalem.linux-foundation.org> (raw)
In-Reply-To: <200811031439.12111.brian.foster@innova-card.com>



On Mon, 3 Nov 2008, Brian Foster wrote:
> 
>   A colleague and I recently wanted to examine the
>  history in a broad sense without worrying too much
>  about the individual commits.  What we (think we)
>  wanted is a ‘gitk --all’ history graph showing only
>  “named” historical points;

Ok, this is actually really easy to do with git. We have all the 
infrastructure in place, and what you're asking for is fundamentally 
really just an odd form of commit history simplification. Instead of 
comparing the *contents* of the commits (the trees) to see if they are 
interesting, you'd only check if there is a decoration (ie a tag or a 
branch) pointing to the commit.

I'll post a simple series of four commits in a moment. They're all 
trivial, and the first three are just setting stuff up (in fact, the very 
first one is a commit I've already posted, and it's technically totally 
unrelated, but since it touches the same area as one of the other ones, 
I'm too lazy to try to separate it out).

Patchbombing to commence in 5.. 4.. 3.. 2.. 1..

		Linus

  parent reply	other threads:[~2008-11-03 19:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-03 13:39 [Q] Abbreviated history graph? Brian Foster
2008-11-03 14:20 ` Santi Béjar
2008-11-03 14:55   ` Santi Béjar
2008-11-03 15:46   ` Brian Foster
2008-11-03 16:08     ` Santi Béjar
2008-11-03 19:32 ` Linus Torvalds [this message]
2008-11-03 19:33   ` [PATCH 1/4] Add a 'source' decorator for commits Linus Torvalds
2008-11-03 19:35     ` [PATCH 2/4] revision: make tree comparison functions take commits rather than trees Linus Torvalds
2008-11-03 19:39       ` [PATCH 3/4] Make '--decorate' set an explicit 'show_decorations' flag Linus Torvalds
2008-11-03 19:43         ` [PATCH 4/4] Add support for 'namespace' history simplification Linus Torvalds
2008-11-03 21:45           ` Santi Béjar
2008-11-03 22:05             ` Linus Torvalds
2008-11-03 22:34               ` Santi Béjar
2008-11-03 22:28           ` Robin Rosenberg
2008-11-04 21:33           ` Clemens Buchacher
2008-11-03 20:15   ` [Q] Abbreviated history graph? Linus Torvalds
2008-11-03 20:34     ` Linus Torvalds
2008-11-04  8:45     ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.2.00.0811031129060.3419@nehalem.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=brian.foster@innova-card.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox