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

Re: [RFC/PATCH 2/4] Teach the --multiple option to 'git fetch'

From
Jay Soffian <jaysoffian@gmail.com>
Date
Nov 9, 2009, 00:59 UTC
Message-ID
<76718490911081659u318ea362l29342a9b3d90f03f@mail.gmail.com>
In-Reply-To
<4AF6E7DE.1020201@gmail.com>
2009/11/8 Björn Gustavsson <bgustavsson@gmail.com>:
> Add the --multiple option to specify that all arguments are either
> groups or remotes. The primary reason for adding this option is
> to allow us to re-implement 'git remote update' using fetch.

Can't this be determined automagically by inspecting the arguments? I believe there can be two unambiguous usages:

a) git fetch <repository> <refspec>... b) git fetch <repository>...

If there is more than one argument, either:

a) arguments 2...N must be refpecs (i.e., each must contain a colon) b) arguments 2...N must NOT be refspecs

"The format of a <refspec> parameter is an optional plus +, followed by the source ref <src>, followed by a colon :, followed by the destination ref <dst>."

j.
Previous: Björn GustavssonNext: Jeff King
Message 2 of 4 in “Teach the --multiple option to 'git fetch'”
  1. 2/4 Teach the --multiple option to 'git fetch'Björn Gustavsson, Nov 8, 2009
  2. Jay SoffianNov 9, 2009
  3. Jeff KingNov 9, 2009
  4. Björn GustavssonNov 9, 2009

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.