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

Re: What's cooking in git.git (May 2011, #04; Sun, 8)

From
Elijah Newren <newren@gmail.com>
Date
May 18, 2011, 03:57 UTC
Message-ID
<BANLkTimQQPad-Sg0=KnEsKowfUJjODKD7A@mail.gmail.com>
In-Reply-To
<7vk4dql7oq.fsf@alter.siamese.dyndns.org>
On Mon, May 16, 2011 at 2:19 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 6 quoted lines
> I am aware of an issue around the merge-recursive area reported by you on
> May 3rd (Message-ID: <BANLkTimcRbuYzSp+MM-vsvxoWhAS8Jvo8Q@mail.gmail.com>,
> $gmane/172617) [*1*]. I had an impression that the guilty party pointed at
> by the bisection was already looking into it.
>
> Elijah, any progress on that one?

Sorry, no, I was struggling to find time. However, I was just successful today in making it so I can take care of some of these things on work time instead of always trying to find spare time to do it. That should help tremendously; expect an update in a week.

Previous: Junio C Hamano
Message 4 of 4 in “What's cooking in git.git (May 2011, #04; Sun, 8)”
  1. Junio C HamanoMay 9, 2011
  2. CiaranMay 9, 2011
  3. Junio C HamanoMay 16, 2011
  4. Elijah NewrenMay 18, 2011

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.