From: Paul Mackerras <paulus@samba.org>
To: "Marco Costalba" <mcostalba@gmail.com>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>, git@vger.kernel.org
Subject: Re: [RFC PATCH] Make gitk use --early-output
Date: Sun, 4 Nov 2007 22:04:09 +1100 [thread overview]
Message-ID: <18221.42793.38389.359621@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <e5bfff550711040237s250bcec0iddf1ebdc616e0bbf@mail.gmail.com>
Marco Costalba writes:
> On 11/4/07, Paul Mackerras <paulus@samba.org> wrote:
> >
> > set vnextroot($view) 0
> > - set order "--topo-order"
> > + set order "--early-output=50"
>
> But --early-output does not imply --topo-order, I guess...
Look here in Linus' patch:
+ if (!prefixcmp(arg, "--early-output")) {
+ int count = 100;
+ switch (arg[14]) {
+ case '=':
+ count = atoi(arg+15);
+ /* Fallthrough */
+ case 0:
+ revs->topo_order = 1;
+ revs->early_output = count;
+ continue;
+ }
+ }
So yes, --early-output does imply --topo-order.
> P.S: Why did you choose not let git log (i.e. Linus) to handle the
> default number of commits?
>
> "--early-output=50" instead of just "--early-output"
Because I was thinking of adding a control in the edit/preferences
window for it later on.
Paul.
next prev parent reply other threads:[~2007-11-04 11:29 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
2007-11-04 10:37 ` Marco Costalba
2007-11-04 11:04 ` Paul Mackerras [this message]
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=18221.42793.38389.359621@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=git@vger.kernel.org \
--cc=mcostalba@gmail.com \
--cc=torvalds@linux-foundation.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).