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

Re: [PATCH] branch: do not attempt to track HEAD implicitly

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 17, 2010, 05:55 UTC
Message-ID
<7vsjxxj640.fsf@alter.siamese.dyndns.org>
In-Reply-To
<201012151626.35366.trast@student.ethz.ch>
Thomas Rast <trast@student.ethz.ch> writes:
Show 9 quoted lines
> Martin von Zweigbergk wrote:
>> On Tue, Dec 14, 2010 at 1:38 PM, Thomas Rast <trast@student.ethz.ch> wrote:
>> > Silently drop the HEAD candidate in the implicit (i.e. without -t
>> > flag) case, so that the branch starts out without an upstream.
>> 
>> Thanks. This has been on my todo list for a while.
>> 
>> Should it only check for HEAD? How about ORIG_HEAD and FETCH_HEAD?
>> Simply anything outside of refs/ maybe? Would that make sense?

I was tempted to say "limit to refs/heads/ and refs/remotes/" but perhaps people have custom namespaces defined in refs/ hierarchy and for some of them the tracking may make sense. How about ignoring the implicit track if the ref does not begin with refs/ to cover the obvious ones like HEAD, FETCH_HEAD, etc.?

Previous: Martin von Zweigbergk
Message 5 of 5 in “branch: do not attempt to track HEAD implicitly”
  1. branch: do not attempt to track HEAD implicitlyThomas Rast, Dec 14, 2010
  2. Martin von ZweigbergkDec 15, 2010
  3. Thomas RastDec 15, 2010
  4. Martin von ZweigbergkDec 15, 2010
  5. Junio C HamanoDec 17, 2010

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.