From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Jim Cromie <jim.cromie@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: skipping commits via commit-msg contents
Date: Mon, 12 Jul 2010 20:35:18 +0200 [thread overview]
Message-ID: <20100712183518.GE17630@debian> (raw)
In-Reply-To: <AANLkTikYcODU96J-cVYCIad1yrd5zGklVj2OV4UT2PxC@mail.gmail.com>
Hi Jim,
Jim Cromie writes:
> sometimes its desirable to commit incomplete work separately,
> for example a struct change thats intended to get compiler to report
> where changes are needed.
>
> 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.
>
> This would also allow rebasing a patchset to markup crappy commits
> which need further work.
This is perhaps not exactly what you want, but I thought I'd mention
it anyway: I usually prefix commit messages of temporary commits with
a "fixup! " or "squash! " and then use the `--autosquash` feature of
`git rebase --interactive` in a new branch before running `git
bisect`.
-- Ram
next prev parent reply other threads:[~2010-07-12 18:33 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 [this message]
2010-07-12 19:02 ` Jonathan Nieder
2010-07-12 19:56 ` Jim Cromie
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=20100712183518.GE17630@debian \
--to=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=jim.cromie@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).