From: "Björn Gustavsson" <bgustavsson@gmail.com>
To: Tay Ray Chuan <rctay89@gmail.com>
Cc: YONETANI Tomokazu <qhwt+git@les.ath.cx>, git@vger.kernel.org
Subject: Re: 65c042d4 broke `remote update' without named group
Date: Fri, 1 Jan 2010 10:14:28 +0100 [thread overview]
Message-ID: <6672d0161001010114g1979eba0pf7de8a78cf979b7c@mail.gmail.com> (raw)
In-Reply-To: <be6fef0d1001010100u7ebf25beydd2ff11ef71a9d66@mail.gmail.com>
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
prev parent reply other threads:[~2010-01-01 9:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6672d0161001010114g1979eba0pf7de8a78cf979b7c@mail.gmail.com \
--to=bgustavsson@gmail.com \
--cc=git@vger.kernel.org \
--cc=qhwt+git@les.ath.cx \
--cc=rctay89@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).