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

Re: [PATCH] git-remote exclude

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jan 15, 2007, 10:23 UTC
Message-ID
<Pine.LNX.4.63.0701151118400.22628@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<45AA44D6.6080605@gmail.com>
Hi,
On Mon, 15 Jan 2007, Quy Tonthat wrote:
> "git-remote exclude" can be used to prevent one or more unwanted remote 
> branches from being tracked. After, for example,
>     $ git-remote origin exclude man html
> "git-fetch origin" will no longer fetch origin/man and origin/html.
That is not what your patch does.

It rewrites the "remote.$name.fetch" entries so that those branches are not _updated_, but they are _fetched_ nevertheless.

But then, I don't really see _why_ you would want such a solution. After all, you are more likely to be interested in _specific_ branches, rather than all branches _except_ a few.

IMHO "git remote expand <name>" to expand the wildcards and "git remote copy <dest> <src>" would be more useful.

Ciao, Dscho

Previous: Quy TonthatNext: Andy Parkins
Message 2 of 10 in “git-remote exclude”
  1. git-remote excludeQuy Tonthat, Jan 14, 2007
  2. Johannes SchindelinJan 15, 2007
  3. Andy ParkinsJan 15, 2007
  4. Jakub NarebskiJan 15, 2007
  5. Junio C HamanoJan 15, 2007
  6. Andy ParkinsJan 16, 2007
  7. Johannes SchindelinJan 16, 2007
  8. Quy TonthatJan 17, 2007
  9. Johannes SchindelinJan 17, 2007
  10. Quy TonthatJan 17, 2007

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.