Andrew Ardill <> writes:

> On 14 September 2012 04:06, Junio C Hamano <> wrote:
>> Andrew Ardill <> writes:
>>> <short-branch-description>
>>>   <long-branch-description>
>>>   <notes>
>>>   <next-steps>
>>>   * <branch-name> (<creation-date>) <number-of-commits>
>>>     (<merge-status>)
>>>    [list-of-commits]
>>>     (<branch-usage>)
>> I do not see how it makes any sense to have the "This is where the
>> section begins with, and its name is this" line in the middle of a
>> block indented in such a way.  Care to explain?
> I'm not quite sure what aspect you are referring to,...

Just this part, as I do not have much time.  Here is your reordered
one I will reject:

  A > jc/maint-blame-no-such-path
    >   "git blame MAKEFILE" run in a history that has "Makefile" but not
    >   "MAKEFILE" should say "No such file MAKEFILE in HEAD", but got
    >   confused on a case insensitive filesystem.
  B >   * jc/maint-blame-no-such-path (2012-09-10) 1 commit
    >    - blame $path: avoid getting fooled by case insensitive filesystems

I was noting that B which *is* formatted as a header line (it EVEN
has a leading asterisk to make it clear that it begins something
new) is in the middle, and you added a redundant A that is not even
marked clearly as a header line.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to
More majordomo info at

Reply via email to