From: Richard Riley <rileyrg@googlemail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: ding@gnus.org, ding-announce@gnus.org
Subject: Re: No Gnus v0.11 is released
Date: Mon, 21 Feb 2011 14:59:03 +0100 [thread overview]
Message-ID: <ler5b17al4.fsf@news.eternal-september.org> (raw)
In-Reply-To: <87wrkukqrt.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 20 Feb 2011 19:39:53 -0800")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Long time, no release. The last one was the traditional release at
> 2008-05-01. That's like a million years ago.
>
> I'll start doing these releases more often now -- but without doing
> tar balls, and without posting diffs. These really aren't that
> interesting any more, I think, since you can just download any version
> you want from git.
>
> So in the future, I'll do a release whenever I feel that development
> Gnus is more stable than usual. So they won't be done when there are
> lots of bright, shiny, new, breakable stuff included, but when it's been
> shown to work at least somewhat.
>
> Get it by saying
>
> git clone http://git.gnus.org/gnus.git && git checkout n0-11
>
> ChangeLog since last release has been removed since it's 8K lines.
Just as a note, it needs a "cd gnus" there. And then "make" doesn't work
saying it needs a target.
next prev parent reply other threads:[~2011-02-21 13:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 3:39 Lars Ingebrigtsen
2011-02-21 7:59 ` Didier Verna
2011-02-21 9:22 ` Lars Ingebrigtsen
2011-02-21 10:56 ` Lars Ingebrigtsen
2011-02-21 12:23 ` Didier Verna
2011-02-21 22:45 ` Lars Ingebrigtsen
2011-02-22 22:04 ` Ted Zlatanov
2011-02-23 8:41 ` Lars Ingebrigtsen
2011-02-23 15:06 ` Ted Zlatanov
2011-02-21 13:59 ` Richard Riley [this message]
2011-02-21 17:44 ` Richard Riley
2011-02-21 23:21 ` Lars Ingebrigtsen
2011-02-21 16:09 ` Wes Hardaker
2011-02-21 23:21 ` Lars Ingebrigtsen
2011-02-21 17:50 ` Simon Josefsson
2011-02-21 23:22 ` Lars Ingebrigtsen
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=ler5b17al4.fsf@news.eternal-september.org \
--to=rileyrg@googlemail.com \
--cc=ding-announce@gnus.org \
--cc=ding@gnus.org \
--cc=larsi@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).