* 65c042d4 broke `remote update' without named group
@ 2009-12-29 23:49 YONETANI Tomokazu
2010-01-01 9:00 ` Tay Ray Chuan
0 siblings, 1 reply; 3+ messages in thread
From: YONETANI Tomokazu @ 2009-12-29 23:49 UTC (permalink / raw)
To: git
Hello.
It seems that with 65c042d4 (and v1.6.6), git-remote update without
specifying a group on the command line ends up with the following error
message if you define remotes.default in the config file:
$ git remote update
fatal: 'default' does not appear to be a git repository
fatal: The remote end hung up unexpectedly
The document still says that when you don't specify the named group,
remotes.default in the configuration will get used, so this should work
(and it used to work with v1.6.4).
After the commit 65c042d4, the commands are translated as follows:
$ git remote update
==> git-fetch default (with remotes.default defined) NG
==> git-fetch --all (without remotes.default defined) OK
$ git remote update default
==> git-fetch --multiple default OK
So just adding "--multiple" in front of "default" in the first case
above should fix it.
Best regards,
YONETANI Tomokazu.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: 65c042d4 broke `remote update' without named group
2009-12-29 23:49 65c042d4 broke `remote update' without named group YONETANI Tomokazu
@ 2010-01-01 9:00 ` Tay Ray Chuan
2010-01-01 9:14 ` Björn Gustavsson
0 siblings, 1 reply; 3+ messages in thread
From: Tay Ray Chuan @ 2010-01-01 9:00 UTC (permalink / raw)
To: YONETANI Tomokazu; +Cc: Björn Gustavsson, git
Hi,
On Wed, Dec 30, 2009 at 7:49 AM, YONETANI Tomokazu <qhwt+git@les.ath.cx> wrote:
> Hello.
> It seems that with 65c042d4 (and v1.6.6), git-remote update without
> specifying a group on the command line ends up with the following error
> message if you define remotes.default in the config file:
> $ git remote update
> fatal: 'default' does not appear to be a git repository
> fatal: The remote end hung up unexpectedly
>
> The document still says that when you don't specify the named group,
> remotes.default in the configuration will get used, so this should work
> (and it used to work with v1.6.4).
>
> After the commit 65c042d4, the commands are translated as follows:
> $ git remote update
> ==> git-fetch default (with remotes.default defined) NG
> ==> git-fetch --all (without remotes.default defined) OK
>
> $ git remote update default
> ==> git-fetch --multiple default OK
>
> So just adding "--multiple" in front of "default" in the first case
> above should fix it.
Björn (added to Cc list), you seem to have been the main author of
'bg/fetch-multi', do you have any idea on this?
--
Cheers,
Ray Chuan
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: 65c042d4 broke `remote update' without named group
2010-01-01 9:00 ` Tay Ray Chuan
@ 2010-01-01 9:14 ` Björn Gustavsson
0 siblings, 0 replies; 3+ messages in thread
From: Björn Gustavsson @ 2010-01-01 9:14 UTC (permalink / raw)
To: Tay Ray Chuan; +Cc: YONETANI Tomokazu, git
2010/1/1 Tay Ray Chuan <rctay89@gmail.com>:
> Björn (added to Cc list), you seem to have been the main author of
> 'bg/fetch-multi', do you have any idea on this?
Yes. I have fixed the problem and my correction is included in
the latest 'pu' (bg/maint-remote-update-default).
--
Björn Gustavsson, Erlang/OTP, Ericsson AB
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-01-01 9:14 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-12-29 23:49 65c042d4 broke `remote update' without named group YONETANI Tomokazu
2010-01-01 9:00 ` Tay Ray Chuan
2010-01-01 9:14 ` Björn Gustavsson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).