From: Jonathan Nieder <jrnieder@gmail.com>
To: Marc Branchaud <marcnarc@xiplink.com>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git v1.8.4.1
Date: Fri, 27 Sep 2013 13:38:11 -0700 [thread overview]
Message-ID: <20130927203811.GM9464@google.com> (raw)
In-Reply-To: <5245E3BD.60703@xiplink.com>
Marc Branchaud wrote:
> On 13-09-27 02:52 PM, Jonathan Nieder wrote:
>> The following public repositories all have a copy of the v1.8.4.1
>> tag and the maint branch that the tag points at:
>>
>> url = https://googlers.googlesource.com/jrn/git
>> url = git://repo.or.cz/git/jrn.git
>> url = git://gitorious.org/git/jrn.git
>> url = https://github.com/jrn/git
>
> Are none of Junio's regular repos going to be updated while he's on vacation?
Yes, that's right.
> I don't think it's a big deal if they're not, though some mention of it in
> this annoucement would've been appreciated
True. Next time. ;-)
Thanks,
Jonathan
next prev parent reply other threads:[~2013-09-27 20:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 18:52 [ANNOUNCE] Git v1.8.4.1 Jonathan Nieder
2013-09-27 19:59 ` Marc Branchaud
2013-09-27 20:38 ` Jonathan Nieder [this message]
2013-09-28 12:09 ` Steffen Prohaska
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=20130927203811.GM9464@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=marcnarc@xiplink.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).