From: Linus Torvalds <torvalds@linux-foundation.org>
To: David Kastrup <dak@gnu.org>
Cc: git@vger.kernel.org
Subject: Re: Can I have this, pretty please?
Date: Sun, 12 Aug 2007 12:59:48 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.999.0708121255230.30176@woody.linux-foundation.org> (raw)
In-Reply-To: <85wsw0mt77.fsf@lola.goethe.zz>
On Sun, 12 Aug 2007, David Kastrup wrote:
> >
> > So, use "git log --pretty=oneline" instead, which doesn't have the
> > expense.
>
> Yes, like managing a manual with grep is all one needs. git log
> --pretty=oneline provides just the commit headers, but offers no way
> to jump into the commits themselves and back easily.
You misunderstand.
I was suggesting you do a *tool* that bases its listing on
--pretty=oneline, and then goes from there.
If you don't show the graph anyway, all the complex and expensive things
that "git-rev-list --topo-order" does is pretty much totally useless.
You're going to show the commits as a list anyway, and then when you
*select* one commit for closer inspection, you can then try to do a better
job at that point of doing the reachability (ie parenthood is trivial, and
the branch reachability is cheap if it's close to the tip of the tree,
which it would almost always be).
The real problem with the topological sort is that it requires you to have
the full history. That not only makes everything pretty big, it also means
that the startup cost is bad, since you can't do things incrementally.
But if you have a client that is incremental anyway, almost all of that
goes away.
Linus
next prev parent reply other threads:[~2007-08-12 20:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-12 13:23 Can I have this, pretty please? David Kastrup
2007-08-12 14:21 ` Steven Grimm
2007-08-12 16:40 ` David Kastrup
2007-08-12 18:38 ` Linus Torvalds
2007-08-12 18:48 ` Linus Torvalds
2007-08-12 19:28 ` Jon Smirl
2007-08-12 19:45 ` Linus Torvalds
2007-08-12 19:48 ` David Kastrup
2007-08-12 19:29 ` David Kastrup
2007-08-12 19:51 ` Uwe Kleine-König
2007-08-12 20:04 ` David Kastrup
2007-08-12 20:21 ` Linus Torvalds
2007-08-12 19:53 ` Linus Torvalds
2007-08-12 20:10 ` David Kastrup
2007-08-13 0:22 ` Paul Mackerras
2007-08-13 5:49 ` David Kastrup
2007-08-12 19:10 ` David Kastrup
2007-08-12 19:24 ` Linus Torvalds
2007-08-12 19:46 ` David Kastrup
2007-08-12 19:59 ` Linus Torvalds [this message]
2007-08-12 20:30 ` David Kastrup
2007-08-12 20:58 ` Govind Salinas
2007-08-12 21:35 ` David Kastrup
2007-08-12 22:17 ` Martin Langhoff
2007-08-12 22:54 ` David Kastrup
2007-08-12 20:02 ` Jeff King
2007-08-12 20:09 ` Jeff King
2007-08-12 21:51 ` David Kastrup
2007-08-12 23:10 ` Jeff King
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.0.999.0708121255230.30176@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=dak@gnu.org \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).