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

Re: Getting new branches from remote repo.

From
Karl Hasselström <kha@treskal.com>
Date
Nov 13, 2006, 17:53 UTC
Message-ID
<20061113175354.GA16094@diana.vm.bytemark.co.uk>
In-Reply-To
<20061113174457.GA16979@spearce.org>
On 2006-11-13 12:44:57 -0500, Shawn Pearce wrote:
Show 9 quoted lines
> Karl Hasselström <kha@treskal.com> wrote:
>
> > There really should be a flag to make git fetch do this job. And
> > if we use separate remotes, the flag should probably default to
> > "on".
>
> And also to automatically stop fetching any branch which is no
> longer listed on the remote system, rather than reporting a "Fetch
> failure".
Yes.
> I probably would keep the local ref (they are cheap) just in case
> the user was counting on that branch and then the remote system
> pulled the rug out from under them. :-)

Sounds like good default behavior. But I smell the potential for another command flag here. :-)

-- 
Karl Hasselström, kha@treskal.com
Previous: Shawn PearceNext: Junio C Hamano
Message 7 of 9 in “Getting new branches from remote repo.”
  1. Alexander LitvinovNov 13, 2006
  2. Junio C HamanoNov 13, 2006
  3. Alexander LitvinovNov 13, 2006
  4. Karl HasselströmNov 13, 2006
  5. Matthias HopfNov 13, 2006
  6. Shawn PearceNov 13, 2006
  7. Karl HasselströmNov 13, 2006
  8. Junio C HamanoNov 13, 2006
  9. Jakub NarebskiNov 13, 2006

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.