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

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

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 16, 2015, 16:04 UTC
Message-ID
<xmqqio7as643.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<16A99EC6028D41FFB0D36D4A1945B113@PhilipOakley>
"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.
Previous: Philip Oakley
Message 2 of 2 in “Re: What's cooking in git.git (Sep 2015, #03; Mon, 14)”
  1. Philip OakleySep 15, 2015
  2. Junio C HamanoSep 16, 2015

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.