From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding-announce@gnus.org
Cc: ding@gnus.org
Subject: Re: Ma Gnus v0.5 is released
Date: Wed, 02 May 2012 00:02:08 +0200 [thread overview]
Message-ID: <m362cf36hr.fsf@stories.gnus.org> (raw)
In-Reply-To: <m3ehr336mc.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Tue, 01 May 2012 23:59:39 +0200")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> The traditional (and almost late) May 1st release!
>
> Get it by saying
>
> git clone http://git.gnus.org/gnus.git && cd gnus && git checkout m0-4
>
> or download the release from
>
> http://git.gnus.org/cgit/gnus.git/snapshot/gnus-m0-4.zip
And in my hurry I forgot to fix the release number here. So it was
really m0-5 that was released...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
prev parent reply other threads:[~2012-05-01 22:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 21:59 Ma Gnus v0.4 " Lars Magne Ingebrigtsen
2012-05-01 22:02 ` Lars Magne Ingebrigtsen [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=m362cf36hr.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=ding-announce@gnus.org \
--cc=ding@gnus.org \
/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).