On Fri, 11 Nov 2011, Junio C Hamano wrote:
> Jakub Narebski <jnareb@xxxxxxxxx> writes:
>> Junio C Hamano <gitster@xxxxxxxxx> writes:
>>> Felipe Contreras <felipe.contreras@xxxxxxxxx> writes:
>>>>
>>>> Perhaps these 'git remote' commands should be removed in 1.8 then.
>>>
>>> It is true that it was a long-term goal to deprecate many parts of the
>>> "git remote" script that started as a hack to scratch itches "git fetch"
>>> in the older days did not directly scratch for people, e.g. fetching from
>>> multiple remotes in one go.
>>>
>>> I do not think 1.7.X series to 1.8 is a big enough jump to remove
>>> duplicated features, though.
>>
>> I am using "git remote update" to fetch a _subset_ of remotes;
>> does "git fetch" offers such feature already?
>
> Heh, look at builtin/remote.c::update() and report what you see. It just
> calls into "git fetch" and let the command fetch either from a single
> repository or from a remote group. "git remote update" is not even aware
> of the remote groups; the expansion is done by "git fetch".
>
> Whoever added "multiple repositories" feature to "git fetch" in order to
> support "remote update <group>" apparently under-documented it.
Well, it is documented in git-fetch(1), though in slightly piecemeal
fashion.
One difference is that "git remote update" defaults to "default" group
if it is defined, and to "--all" if it isn't. With "git fetch --multiple"
you have to specify it explicitly ("git fetch --multiple" is a no-op,
I think).
--
Jakub Narebski
Poland
--
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