threads / discuss / 40359

Re: What's cooking in git.git (Sep 2015, #03; Mon, 14)

Subject: Re: What's cooking in git.git (Sep 2015, #03; Mon, 14)

## tl;dr

2 messages between Sep 15, 2015 and Sep 16, 2015.

replies: 1people: 2as markdown or json

Philip Oakley· Sep 15, 2015, 19:08 UTC · lore

Oops..
From: "Philip Oakley" <philipoakley@iee.org>

Show 15 quoted lines

>> [New Topics]
>
>> * po/doc-branch-desc (2015-09-14) 1 commit
>>  (merged to 'next' on 2015-09-14 at 4934a96)
>> + doc: show usage of branch description
>>
>> The branch descriptions that are set with "git
>> branch --edit-description"
>> option were used in many places but they weren't clearly documented.
>>
>> Will merge to 'master'.
>>
> Thanks.
> Shall I just rework/resend the V2 patch-up ($gmane/277829) that also
> links to 'merge's' usage as a fresh patch (would be tonight UK)?

I now see that the full V2 patch is already there at 4934a96. I'd mistakenly just compared your note to the slightly fuller V2 commit message and in the morning rush hadn't had time to check.

Sorry for the noise.

Philip

Junio C Hamano· Sep 16, 2015, 16:04 UTC · re: Philip Oakley · lore

"Philip Oakley" <philipoakley@iee.org> writes:

Show 6 quoted lines

> Oops..
> ...
>> Shall I just rework/resend the V2 patch-up ($gmane/277829) that also
>> links to 'merge's' usage as a fresh patch (would be tonight UK)?
>
> I now see that the full V2 patch is already there at 4934a96.

OK.  I was wondering what I missed.  4934a96^2 is a copy of your v2.

> I'd mistakenly just compared your note to the slightly fuller V2 commit
> message and in the morning rush hadn't had time to check.
>
> Sorry for the noise.

Thanks for being careful.