From: Simon Josefsson <simon@josefsson.org>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Gnus development - Emacs 23 feature freeze, Emacs 22.3 pretest
Date: Thu, 02 Oct 2008 12:11:15 +0200 [thread overview]
Message-ID: <87ljx7joho.fsf@mocca.josefsson.org> (raw)
In-Reply-To: <86sksxt69z.fsf@lifelogs.com> (Ted Zlatanov's message of "Fri, 22 Aug 2008 10:32:08 -0500")
Ted Zlatanov <tzz@lifelogs.com> writes:
> On Fri, 22 Aug 2008 14:20:07 +0200 Paul R <paul.r.ml@gmail.com> wrote:
>
> PR> On Fri, 22 Aug 2008 13:49:22 +0200, Reiner Steib <reinersteib+gmane@imap.cc> said:
> Reiner> Hi, we need to decide how to continue Gnus development because
> Reiner> of the Emacs 23 feature freeze.
>
> PR> On side notes, is there a place other than the source tree where
> PR> I could read the changelog please ?
>
> You can look at nntp+news.gnus.org:gnus.commits which has every commit
> message.
I believe some commits messages are lost though, I get moderator bounces
when I commit every blue moon. Maybe they end up in a queue somewhere
though, but I'm not sure.
/Simon
next prev parent reply other threads:[~2008-10-02 10:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 11:49 Reiner Steib
2008-08-22 12:20 ` Paul R
2008-08-22 12:56 ` ChangeLog (was: Gnus development - Emacs 23 feature freeze, Emacs 22.3 pretest) Reiner Steib
2008-08-22 15:32 ` Gnus development - Emacs 23 feature freeze, Emacs 22.3 pretest Ted Zlatanov
2008-10-02 10:11 ` Simon Josefsson [this message]
2008-10-02 14:38 ` Jason L Tibbitts III
2008-08-22 15:38 ` Ted Zlatanov
2008-08-22 15:49 ` David Engster
2008-08-27 23:00 ` Miles Bader
2008-11-03 20:10 ` Reiner Steib
2008-08-22 16:12 ` Sven Joachim
2008-11-03 20:28 ` Reiner Steib
2008-08-24 20:10 ` Romain Francoise
2008-11-03 20:34 ` Reiner Steib
2008-10-10 18:21 ` Gnus 5.10.12 release plan (was: Gnus development - Emacs 23 feature freeze, Emacs 22.3 pretest) Reiner Steib
2008-11-03 20:14 ` Gnus development - Emacs 23 feature freeze, Emacs 22.3 pretest Reiner Steib
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=87ljx7joho.fsf@mocca.josefsson.org \
--to=simon@josefsson.org \
--cc=ding@gnus.org \
--cc=tzz@lifelogs.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).