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

Re: FETCH_HEAD documentation vs reality

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 26, 2011, 08:16 UTC
Message-ID
<7vd3bb929n.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20111225173901.GA668@gnu.kitenet.net>
Joey Hess <joey@kitenet.net> writes:
> Or yet another way to fix it would be to make git fetch always write the
> intended FETCH_HEAD first into .git/FETCH_HEAD. (When not in --append mode.)
> This seems like perhaps the best fix,...

Sounds good, if you mean "the first one that is marked as for-merge" by "intended FETCH_HEAD".

Thanks. Please make it so.
Previous: Joey HessNext: Joey Hess
Message 2 of 7 in “FETCH_HEAD documentation vs reality”
  1. Joey HessDec 25, 2011
  2. Junio C HamanoDec 26, 2011
  3. write first for-merge ref to FETCH_HEAD firstJoey Hess, Dec 26, 2011
  4. Junio C HamanoDec 27, 2011
  5. Junio C HamanoJan 3, 2012
  6. Joey HessJan 4, 2012
  7. Junio C HamanoJan 4, 2012

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.