Re: git fetch workflow improvements

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Feb 9, 2008, 14:00 UTC
Message-ID: <alpine.LSU.1.00.0802091357480.11591@racer.site>
In-Reply-To: <20080209132745.GA13997@glandium.org>

Hi,

On Sat, 9 Feb 2008, Mike Hommey wrote:

Show 10 quoted lines

> On Sat, Feb 09, 2008 at 01:20:29PM +0000, Johannes Schindelin wrote:
> 
> > $ git remote update
> 
> BTW, is the following normal?
> 
> $ git remote update origin
> Remote group origin does not exists.
> 
> (there *is* an origin remote)

Straight from the man page:

-- snip -- 'update'::

Fetch updates for a named set of remotes in the repository as defined by remotes.<group>. If a named group is not specified on the command line, the configuration parameter remotes.default will get used; if remotes.default is not defined, all remotes which do not have the configuration parameter remote.<name>.skipDefaultUpdate set to true will be updated. (See linkgit:git-config[1]). -- snap --

To spare you the hassle from looking up the relevant section in git-config.1:

-- snip --
remotes.<group>::
        The list of remotes which are fetched by "git remote update
        <group>".  See linkgit:git-remote[1].
-- snap --

So if you add a group to your config file, like

	[remotes]
		origin = origin kernelorg repoorcz

your

	$ git remote update origin

will succeed.

Hth, Dscho