Re: Cleaning up git user-interface warts

From: Junio C Hamano <junkio@cox.net>
Date: Nov 15, 2006, 17:59 UTC
Message-ID: <7vfyckoaju.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <Pine.LNX.4.64.0611151023160.2591@xanadu.home>

Nicolas Pitre <nico@cam.org> writes:

Show 5 quoted lines

> But again I think it is important that the URL to use must be a per 
> branch attribute i.e. attached to "default/master" and not just 
> "default".  This way someone could add all branches of interest into the 
> "default" group even if they're from different repositories, and a 
> simple  get without any argument would get them all.

I think the "one group per one remote repository" model is a lot easier to explain. At least when I read your first "branch group" proposal that was I thought was going on and I found it quite sensible (and it maps more or less straightforwardly to the way existing .git/refs/remotes is set up by default).

$ 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.