From: Paolo Bonzini <bonzini@gnu.org>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org
Subject: Re: [PATCH 1/9 v4] bisect: add "git bisect replace" subcommand
Date: Fri, 14 Nov 2008 11:03:46 +0100 [thread overview]
Message-ID: <491D4D02.6080004@gnu.org> (raw)
In-Reply-To: <200811141034.06282.chriscool@tuxfamily.org>
>> users could also set up a few
>> special bisect/set-debug-to-1, bisect/remove-cflags-o2 and so on patches
>> that you could use for purposes other than ensuring known bugs are fixed.
>
> In this case it is similar to Junio's proposal. But I think that for changes
> like set-debug-to-1 and remove-cflags-o2, using the right make command
> should be enough.
Yeah, I couldn't think of a better usecase, but you got the idea.
>> Finally, you could have a [bisect] configuration section with entries
>> like "cherry-pick = BROKEN-SHA1 FIX-SHA1" and "git bisect" would apply
>> FIX-SHA1 automatically if the bisect tip were in BROKEN-SHA1..FIX-SHA1.
>
> Yes, but how do you share this between members of a team?
That's a common problem with stuff that goes in .gitconfig. It does not
belong in the repository, though...
Paolo
next prev parent reply other threads:[~2008-11-14 10:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 5:39 [PATCH 1/9 v4] bisect: add "git bisect replace" subcommand Christian Couder
2008-11-11 23:23 ` Junio C Hamano
2008-11-12 14:15 ` Christian Couder
2008-11-13 9:46 ` Junio C Hamano
2008-11-13 17:50 ` Christian Couder
2008-11-13 16:41 ` Paolo Bonzini
2008-11-14 9:34 ` Christian Couder
2008-11-14 10:03 ` Paolo Bonzini [this message]
2008-11-15 14:19 ` Christian Couder
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=491D4D02.6080004@gnu.org \
--to=bonzini@gnu.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=chriscool@tuxfamily.org \
--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).