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

Re: Problem upgrading to 1.4.0

From
PRPavel Roskin <proski@gnu.org>
Date
Jun 13, 2006, 02:33 UTC
Message-ID
<1150165982.4297.88.camel@dv>
In-Reply-To
<7v1wtwh246.fsf@assigned-by-dhcp.cox.net>
On Sat, 2006-06-10 at 19:12 -0700, Junio C Hamano wrote:
> This is the second time this same gotcha caused trouble here.  I
> agree it would be sensible to make git-fetch (which is called by
> git-pull) to detect stale entries in the remotes/origin file and
> remote.origin.fetch configuration items.

And while at that, it would be great to download and keep the list of the remote branches, perhaps when requested with a special switch. It doesn't mean that all of the branches should be fetched, but it would be nice to have a list of the available remove branches somewhere.

As it stands now, this functionality is implemented in git-clone, which it probably not the best place. Users should not be forced to clone the directory again to find out which branches are available.

-- 
Regards,
Pavel Roskin
Previous: Junio C HamanoNext: Sean
Message 3 of 8 in “Problem upgrading to 1.4.0”
  1. Geoff RussellJun 11, 2006
  2. Junio C HamanoJun 11, 2006
  3. Pavel RoskinJun 13, 2006
  4. SeanJun 13, 2006
  5. Pavel RoskinJun 13, 2006
  6. Linus TorvaldsJun 13, 2006
  7. Pavel RoskinJun 13, 2006
  8. Geoff RussellJun 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.