Allow git-remote to update named groups of remotes
commit1918278ea1019553b01297aad2caeed88e9092a4
authorTheodore Ts'o <tytso@mit.edu>
Tue, 20 Feb 2007 20:13:43 +0000 (20 15:13 -0500)
committerJunio C Hamano <junkio@cox.net>
Wed, 21 Feb 2007 07:58:39 +0000 (20 23:58 -0800)
tree3776db2051dfdd63aa4acba8344a2a02af965606
parent7b9a13ece8a1e7c0fd2a82d4bd4fcf0a9ce0e8c4
Allow git-remote to update named groups of remotes

In response to a feature request from Shawn Pearce, this patch allows
a user to update a named group of remotes by using "git remote update
<group>", where the group is defined in the config file by
remotes.<group>.  The default if the named group is not specified is
now fetched group remotes.default, instead of remote.fetch, which is
what had been previously used.

In addition, if remotes.default is not defined, all remotes defined in
the config file will be used, as before, but there is now also
possible to request that a particular repository to be skipped by
default by using the boolean configuration parameter
remote.<name>.skipDefaultUpdate.

Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Signed-off-by: Junio C Hamano <junkio@cox.net>
Documentation/config.txt
Documentation/git-remote.txt
git-remote.perl