From: Jim Cromie <jim.cromie@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org, Christian Couder <chriscool@tuxfamily.org>,
Ramkumar Ramachandra <artagnon@gmail.com>
Subject: Re: skipping commits via commit-msg contents
Date: Mon, 12 Jul 2010 13:56:20 -0600 [thread overview]
Message-ID: <AANLkTikVNpFPBMO_SDIfn-5np42ALI-qGAHTOvlmONxo@mail.gmail.com> (raw)
In-Reply-To: <20100712190203.GA9365@dert.cs.uchicago.edu>
thanks guys,
Ram, not what I want, but good to know..
Jonathan, replace feels like a big hammer for a newbie..
I havent published these, since they need bisection amongst other reasons :-O
and the BUGS also require more -fu to understand than I possess
On Mon, Jul 12, 2010 at 1:02 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:
> Hi Jim,
>
> Jim Cromie wrote:
>
>> if git bisect were to recognize --skip-bisect in the subject line
>> (or in commit-message somewhere, say top or bottom),
>> then bisection could proceed silently past such commits.
>
> In addition to Ram’s suggestion, you might want to look into
> ‘git replace’[1]. It can be useful when the broken commits
> have already been published. It works like this:
>
> git replace <bad commit> <bad commit>^
>
> and then ‘git bisect’ and lower-level commands like git show and
> checkout will silently substitute the parent of the broken commit
> when ever you refer to it.
>
> You can publish the resulting “replace refs” in the refs/replace/*
> namespace and anyone who explicitly chooses to fetch them will be
> able to see the same effect.
>
> Two problems:
>
> - bisect skip is a bit more sophisticated (read: better) than just
> substituting a parent, especially when the commit to be skipped
> is a merge. So it might still make sense to teach bisect to
> respect a refs/notes/skip-bisect note that requests for it
> to skip a specific ref.
This sounds nice.
Notionally, extending it further would be cool -
[jimc@groucho perl-git]$ git notes show 2de9db42d3e578becacbd237bf4f59b432cc82f0
good make test
with this note, Ive told myself that it passes (good), and what it
passes (make test)
I could imagine bisect knowing enough to take that as an implicit start,
unless overridden on a command line, or by a similar note on a later commit.
a note like:
skip-bisect until <tag|commit|branch>
could be cool too, though there may be deeper problems with skipping
entire subranges.
thanks again,
Jim
prev parent reply other threads:[~2010-07-12 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 18:21 skipping commits via commit-msg contents Jim Cromie
2010-07-12 18:35 ` Ramkumar Ramachandra
2010-07-12 19:02 ` Jonathan Nieder
2010-07-12 19:56 ` Jim Cromie [this message]
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=AANLkTikVNpFPBMO_SDIfn-5np42ALI-qGAHTOvlmONxo@mail.gmail.com \
--to=jim.cromie@gmail.com \
--cc=artagnon@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.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).