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

Re: Bug? - Unexpected lock file error

From
EREric Raible <raible@gmail.com>
Date
Sep 6, 2008, 00:05 UTC
Message-ID
<279b37b20809051705o1f00ac4fpfc085fe58fdf5133@mail.gmail.com>
In-Reply-To
<7v63paupd8.fsf@gitster.siamese.dyndns.org>
On Fri, Sep 5, 2008 at 4:47 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 6 quoted lines
> "Eric Raible" <raible@gmail.com> writes:
>
>> If 'empty' has any commits then the merge happens as expected.
>
> I think it is a bug in the git-merge rewritten in C, in "Already
> uptodate!" codepath.

And the ""Already uptodate!" codepath isn't even triggered when we're up-to-date but 'empty' has at even one actual commit. In that case we get a friendly "Already up-to-date" and no fatal error.

Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 7 in “Bug? - Unexpected lock file error”
  1. Eric RaibleSep 5, 2008
  2. Junio C HamanoSep 5, 2008
  3. Eric RaibleSep 6, 2008
  4. Junio C HamanoSep 6, 2008
  5. Miklos VajnaSep 6, 2008
  6. builtin-merge: release the lockfile in try_merge_strategy()Miklos Vajna, Sep 6, 2008
  7. Junio C HamanoSep 7, 2008

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.