git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Paul Mackerras <paulus@samba.org>
Cc: git@vger.kernel.org
Subject: Re: [RFC PATCH] Make gitk use --early-output
Date: Sat, 3 Nov 2007 22:30:06 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.0.999.0711032227420.15101@woody.linux-foundation.org> (raw)
In-Reply-To: <18221.2285.259487.655684@cargo.ozlabs.ibm.com>



On Sun, 4 Nov 2007, Paul Mackerras wrote:
>
> This makes gitk use the --early-output flag on the git log command.
> 
> When gitk sees the "Final output:" line from git log, it goes into a
> mode where it basically just checks that it is getting the commits
> again in the same order as before.  If they are, well and good; if
> not, it truncates its internal list at the point of difference and
> proceeds to read in the commits in the new order from there on, and
> re-does the graph layout if necessary.
> 
> This gives a much more immediate feel to the startup; gitk shows its
> window with the first screenful of commits displayed very quickly this
> way.

Goodie. Seems to work for me. I'll tweak the behaviour of --early-output a 
bit more, because right now if things are really cold in the cache, the 
"--early-output" logic will often trigger with just a single commit in the 
list (because the timeout is so short), but it already seems to work 
pretty well.

		Linus

  parent reply	other threads:[~2007-11-04  5:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-03 23:49 [RFC PATCH] Make gitk use --early-output Paul Mackerras
2007-11-04  2:07 ` Michael J. Cohen
2007-11-04  5:30 ` Linus Torvalds [this message]
2007-11-04 10:37 ` Marco Costalba
2007-11-04 11:04   ` Paul Mackerras
2007-11-04 11:57     ` Marco Costalba
2007-11-04 17:53   ` Linus Torvalds
2007-11-04 18:28 ` David Kastrup

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

  List information: http://vger.kernel.org/majordomo-info.html

* 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.0711032227420.15101@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=git@vger.kernel.org \
    --cc=paulus@samba.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).