Alex Riesen wrote:
> On 2/19/07, Shawn O. Pearce <spearce@xxxxxxxxxxx> wrote:
>> Junio C Hamano <junkio@xxxxxxx> wrote:
>> > "Theodore Ts'o" <tytso@xxxxxxx> writes:
>> >
>> > > This allows users to use the command "git remote update" to update all
>> > > remotes that are being tracked in the repository.
>> >
>> > Sounds like a good idea. Thanks.
>>
>> <personalwishlist>
>>
>> It would be nice to define "gang remotes". For example I want to
>> be able to have:
>>
>> `git fetch cs` == `git fetch cs-one; git fetch cs-two`
>> `git fetch jc` == `git fetch origin; git fetch alt`
>
> I was thinking about something very similar.
>
>> Why? Well, I often have multiple remotes setup to the *same*
>> repository depending on the SSH hostname I want to use to access
>> that repository. This has a lot to do with the way my firewalls
>> are setup and where I'm physically connected at any given time.
>
> For all the same reasons :)
>
>> Yes, I really do have multiple remotes setup to the access the
>> same (remote) physical disk. :)
>>
>> Possible syntax:
>>
>> [remote "cs"]
>> remote = cs-one
>> remote = cs-two
>> [remote "jc"]
>> remote = origin
>> remote = alt
>>
>
> Or :
>
> [remote "jc"]
> url = git://...
> fetch = refs/heads/*:remotes/jc/*
> remote ("include"? "next"?) = origin
>
> (I mean: it can be allowed to mix url/fetch and remote).
>
> And:
>
> [remote "jc"]
> fail = all-fail
> remote = origin
> remote = backup
>
> IOW: the fetch fails only if all fetches fail (with default
> being "fail = first").
Or just allow fetch remotes to have multiple URLs, and fetch from all/try to fetch starting from first.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html