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

Re: [RFC] git-mergetool: show original branch names when possible

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 21, 2007, 21:17 UTC
Message-ID
<7vir78oadg.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20070821205503.GA16777@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 13 quoted lines
> On Tue, Aug 21, 2007 at 04:59:43PM +0200, Jan Hudec wrote:
>
>> >   1. It does not handle pulls which have no tracking branch (the only
>> >      ref we have is FETCH_HEAD, which is not a useful name :) ).
>> 
>> If there's no useful name, than it's probably hard to do anything at all
>> about it. Though FETCH_HEAD is not all that useless -- it at least says it is
>> that that you pull.
>
> But there _is_ a useful name, it's just not a ref (it's the information
> from FETCH_HEAD "branch 'foo' of git://..."). In this case,
> git-mergetool could pull it out of FETCH_HEAD, as well, but I feel like
> we're starting to make a lot of fragile cross-tool assumptions.

Isn't the label "FETCH_HEAD" itself clear enough, without even looking at it to see which commit it is?

Previous: Jeff King
Message 8 of 8 in “[RFC] git-mergetool: show original branch names when possible”
  1. Jeff KingAug 20, 2007
  2. Junio C HamanoAug 20, 2007
  3. Jeff KingAug 20, 2007
  4. Jan HudecAug 20, 2007
  5. Jeff KingAug 21, 2007
  6. Jan HudecAug 21, 2007
  7. Jeff KingAug 21, 2007
  8. Junio C HamanoAug 21, 2007

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.