git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: git-bisect feature suggestion: "git-bisect diff"
Date: Fri, 7 Dec 2007 12:21:59 +0100	[thread overview]
Message-ID: <20071207112159.GA11035@elte.hu> (raw)
In-Reply-To: <7vwsrq3iox.fsf@gitster.siamese.dyndns.org>


* Junio C Hamano <gitster@pobox.com> wrote:

>  (1) When no option is given, and $DISPLAY is set, it continues to
>      spawn gitk as before;
> 
>  (2) When no option is given, and $DISPLAY is unset, "git log" is run
>      to show the range of commits between the bad one and the good 
>      ones;
> 
>  (3) If only "-flag" options are given, "git log <options>" is run.
>      E.g. "git bisect visualize --stat"
> 
>  (4) Otherwise, all of the given options are taken as the initial part
>      of the command line and the commit range expression is given to 
>      that command.  E.g. "git bisect visualize tig" will run "tig" 
>      history viewer to show between the bad one and the good ones.

nice. One small detail though: i frequently ssh to testboxes that have 
DISPLAY set but i want text output. So git-bisect view --text should be 
a special-case perhaps?

	Ingo

  reply	other threads:[~2007-12-07 11:22 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-07  9:34 git-bisect feature suggestion: "git-bisect diff" Ingo Molnar
2007-12-07  9:58 ` Junio C Hamano
2007-12-07 10:25   ` Junio C Hamano
2007-12-07 11:21     ` Ingo Molnar [this message]
2007-12-07 19:28       ` Junio C Hamano
2007-12-07 19:46         ` Ingo Molnar
2007-12-07 21:34     ` Jeff King
2007-12-07 21:35       ` Jeff King
2007-12-07 21:44         ` Junio C Hamano
2007-12-07 21:55           ` Jeff King
2007-12-07 22:03             ` Junio C Hamano
2007-12-07 22:07               ` Jeff King
2007-12-08  2:54                 ` Junio C Hamano
2007-12-08  5:36 ` Christian Couder
2007-12-08 15:29   ` Ingo Molnar
2007-12-09  5:33     ` git-bisect run make -j64 kernel/ (was Re: git-bisect feature suggestion: "git-bisect diff") Christian Couder
2007-12-12  9:43       ` Ingo Molnar
2007-12-11  9:24   ` git-bisect feature suggestion: "git-bisect diff" Ingo Molnar
2007-12-11  9:29     ` Pierre Habouzit
2007-12-11 10:13       ` Jakub Narebski
2007-12-11 11:59         ` Pierre Habouzit
2007-12-11 12:25           ` Jeff King
2007-12-11 12:33             ` Jeff King
2007-12-11 14:05             ` Ingo Molnar
2007-12-11 14:43               ` [PATCH] Invert numbers and names in the git-shortlog summary mode Pierre Habouzit
2007-12-11 14:57                 ` Ingo Molnar
2007-12-11 15:24                   ` Pierre Habouzit
2007-12-11 15:34                     ` Nicolas Pitre
2007-12-11 18:09                       ` Junio C Hamano
2007-12-11 15:48                     ` Ingo Molnar
2007-12-11 16:07                       ` Pierre Habouzit
2007-12-11 16:11                         ` Pierre Habouzit
2007-12-11 21:13                         ` Ingo Molnar
2007-12-11 22:21                           ` Junio C Hamano
2007-12-11 17:58                 ` Junio C Hamano
2007-12-11 10:17       ` git-bisect feature suggestion: "git-bisect diff" Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2007-12-11 22:22 しらいしななこ

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=20071207112159.GA11035@elte.hu \
    --to=mingo@elte.hu \
    --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;
as well as URLs for NNTP newsgroup(s).