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

Re: Working with remotes with (too) many branches

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Feb 21, 2012, 22:43 UTC
Message-ID
<20120221224303.GB31934@burratino>
In-Reply-To
<CAKHWUkY_bEtKoPOiWFz6i2bp-tbekapROOaCYR0k5Ymh0HYMdA@mail.gmail.com>
Hi Philip,
Philip Jägenstedt wrote:
> It seems to me that if one starts out with all branches and then
> "set-branches main footopic", one really does want all other refs to
> go away on the next fetch.

I would expect set-branches to remove the remote-tracking branches that are no longer relevant itself, actually.

Martin, does this seem sensible to you? If so, I'll be happy to look into it in the next few days (or I'll be even happier someone else gets to it first).

Hope that helps, Jonathan

Previous: Philip JägenstedtNext: Junio C Hamano
Message 4 of 5 in “Working with remotes with (too) many branches”
  1. Philip JägenstedtFeb 19, 2012
  2. Junio C HamanoFeb 19, 2012
  3. Philip JägenstedtFeb 21, 2012
  4. Jonathan NiederFeb 21, 2012
  5. Junio C HamanoFeb 21, 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.