From: Jon Seymour <jon.seymour@gmail.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git-rev-list: proper lazy reachability
Date: Wed, 1 Jun 2005 10:14:19 +1000 [thread overview]
Message-ID: <2cfc4032050531171437d5d9eb@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0505310758270.1876@ppc970.osdl.org>
On 6/1/05, Linus Torvalds <torvalds@osdl.org> wrote:
>
>
> On Tue, 31 May 2005, Jon Seymour wrote:
> >
> > A
> > / | \
> > B C D
> > | / /
> > E
> > | \
> > F G
> >
> > and searching for git-rev-list A ^B it would actually be better to stop
> > at E (printing A,B,C,D,E)
>
> Btw, you probably looked at the actual code, so you know this, but maybe
> it wasn't clear to everybody else: the code obviously _will_ look at all
> of ABCDE before it can even decide that it should print out ACD, since it
> really needs to.
I did look at the code and concluded that ACD would be displayed and
simply assumed B would also be displayed. Anyway, you are right, for
the purposes you are interested in neither B nor E are interesting.
>
> But if somebody wanted to actually show this as a _graph_, what you would
> probably want is actually all of ABCDE, except you'd get the "interesting"
> bit separately (ie ACD would be tagged some way). Then you could show a
> sane graph that is colored by whether something is new or not, for
> example. That's absolutely trivial to do wiyth the new rev-list algorithm,
> in case somebody really cares - it's literally just changing the printout
> to show the entries marked "ignored" with some extra marking.
This will also fall pretty naturally out of the --merge-order patch
that I am working on with an appropiate tweak. But I'll shut up about
that until I have code to share...
jon.
next prev parent reply other threads:[~2005-06-01 0:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 1:58 git-rev-list: proper lazy reachability Linus Torvalds
2005-05-31 7:58 ` Jon Seymour
2005-05-31 14:35 ` Linus Torvalds
2005-05-31 15:13 ` Linus Torvalds
2005-06-01 0:14 ` Jon Seymour [this message]
2005-05-31 12:15 ` Paul Mackerras
2005-05-31 14:39 ` Linus Torvalds
2005-05-31 15:23 ` Linus Torvalds
2005-06-01 16:38 ` Matthias Urlichs
2005-06-04 15:01 ` Junio C Hamano
2005-06-04 15:09 ` Thomas Glanzmann
2005-06-04 15:42 ` Linus Torvalds
2005-06-04 15:51 ` Linus Torvalds
2005-06-04 19:30 ` Junio C Hamano
2005-06-04 19:46 ` Petr Baudis
2005-06-04 19:41 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2005-06-01 18:44 Marco Costalba
2005-06-01 19:02 Marco Costalba
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=2cfc4032050531171437d5d9eb@mail.gmail.com \
--to=jon.seymour@gmail.com \
--cc=git@vger.kernel.org \
--cc=jon@blackcubes.dyndns.org \
--cc=torvalds@osdl.org \
/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