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