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

Re: [PATCH] improve doc heading for git-bisect

From
Jakub Narebski <jnareb@gmail.com>
Date
Jun 7, 2008, 09:22 UTC
Message-ID
<m37id1y4zj.fsf@localhost.localdomain>
In-Reply-To
<20080607070637.79B17C7C0E@rwavmlap>
rwa000@gmail.com (Robert Anderson) writes:
> From 7af03a835b7311c501f2147e25f428642fc3acb7 Mon Sep 17 00:00:00 2001

FYI this line is not necessary, and should be removed from git-format-patch output when pasting it to your MUA.

> From: Robert W. Anderson <rwa000@gmail.com>
> Date: Fri, 6 Jun 2008 23:53:37 -0700
> Subject: [PATCH] improve doc heading for git-bisect

FYI the above isn't strictly necessary: if you have 'From:' header set correctly you can simply set subject of email, and put in body the rest of commit message and patch only, without extra mail-like headers.

> Improve awkward heading in git-bisect documentation.
[...]
Show 7 quoted lines
> -Avoiding to test a commit
> -~~~~~~~~~~~~~~~~~~~~~~~~~
> +Changing the revision to test
> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>  
>  If in a middle of bisect session, you know what the bisect suggested
>  to try next is not a good one to test (e.g. the change the commit

It is, I guess, better, but is it the best heading? What we want to describe here is how to deal when bisect stops on commit which cannot be tested (e.g. project does not compile).

-- 
Jakub Narebski
Poland
ShadeHawk on #git
Previous: Robert AndersonNext: Robert Anderson
Message 2 of 8 in “improve doc heading for git-bisect”
  1. improve doc heading for git-bisectRobert Anderson, Jun 7, 2008
  2. Jakub NarebskiJun 7, 2008
  3. Robert AndersonJun 7, 2008
  4. Jakub NarebskiJun 7, 2008
  5. Junio C HamanoJun 7, 2008
  6. Jeff KingJun 8, 2008
  7. Johannes SchindelinJun 8, 2008
  8. Jeff KingJun 8, 2008

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.