git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: skipping commits via commit-msg contents

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
Jul 12, 2010, 18:35 UTC
Message-ID
<20100712183518.GE17630@debian>
In-Reply-To
<AANLkTikYcODU96J-cVYCIad1yrd5zGklVj2OV4UT2PxC@mail.gmail.com>
Hi Jim,
Jim Cromie writes:
Show 10 quoted lines
> 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
Previous: Jim CromieNext: Jonathan Nieder
Message 2 of 4 in “skipping commits via commit-msg contents”
  1. Jim CromieJul 12, 2010
  2. Ramkumar RamachandraJul 12, 2010
  3. Jonathan NiederJul 12, 2010
  4. Jim CromieJul 12, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.