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

Re: [PATCH 1/2] remote: write correct fetch spec when renaming remote 'remote'

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 1, 2011, 03:18 UTC
Message-ID
<7vk49tx84v.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20110901024211.GC31838@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 7 quoted lines
> Actually, I think it's better to be more conservative, and rename only:
>
>   refs/remotes/$OLD/
>
> into
>
>   refs/remotes/$NEW/
Thanks.

I wholeheartedly agree with this. It would let me sleep better if we did this rewriting only when remote.$name.fetch is set exactly to its default value, "+refs/heads/*:refs/origin/$name/*" (it is Ok if the leading '+' is missing, though), and we didn't touch either config nor the existing tracking refs at all otherwise, and gave warning saying we didn't do anything to them.

Previous: Jeff KingNext: Martin von Zweigbergk
Message 7 of 8 in “remote: write correct fetch spec when renaming remote 'remote'”
  1. 1/2 remote: write correct fetch spec when renaming remote 'remote'Martin von Zweigbergk, Sep 1, 2011
  2. 2/2 remote: "rename o foo" should not rename ref "origin/bar"Martin von Zweigbergk, Sep 1, 2011
  3. Jeff KingSep 1, 2011
  4. Martin von ZweigbergkSep 2, 2011
  5. Jeff KingSep 2, 2011
  6. Jeff KingSep 1, 2011
  7. Junio C HamanoSep 1, 2011
  8. Martin von ZweigbergkSep 2, 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.