From: Ted Zlatanov <tzz@lifelogs.com>
To: Christoph Conrad <christoph.conrad@gmx.de>
Cc: <ding@gnus.org>
Subject: Re: Gnus branches and sync with Emacs
Date: Wed, 22 Jul 2009 10:32:48 -0500 [thread overview]
Message-ID: <87k520n36n.fsf@lifelogs.com> (raw)
In-Reply-To: <87ab2xbw9r.fsf@ID-24456.user.uni-berlin.de> (Christoph Conrad's message of "Tue, 21 Jul 2009 22:43:35 +0200")
On Tue, 21 Jul 2009 22:43:35 +0200 Christoph Conrad <christoph.conrad@gmx.de> wrote:
CC> Hi Ted,
>> so I think stability is supposed to be an exception, at least when
>> that was written.
CC> When trunk CVS gnus is meant here: i am using it for several years now,
CC> and for a very long time it has been stable.
I meant stability in the sense of fewer updates to stabilize the source
code (which reminds me of the quip that biology has a word for "stable"
and it's "dead"). Perhaps the right word was "quiescense" :)
I agree the Gnus trunk has been very reliable since I can remember, but
my point is that if I want to put in a bleeding-edge feature I shouldn't
have to wait for the next release.
There's definitely an implicit agreement that no such features should be
pushed if they break current setups or endanger user data, especially if
they are on by default. I am not implying otherwise.
Ted
next prev parent reply other threads:[~2009-07-22 15:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 12:27 Branch for 23.1? David Engster
2009-07-18 20:21 ` Gnus branches and sync with Emacs (was: Branch for 23.1?) Reiner Steib
2009-07-20 17:23 ` Gnus branches and sync with Emacs Ted Zlatanov
2009-07-20 18:18 ` Chong Yidong
2009-07-20 20:42 ` Reiner Steib
2009-07-21 1:06 ` Stefan Monnier
2009-07-21 16:09 ` Ted Zlatanov
2009-07-21 17:27 ` Reiner Steib
2009-07-21 20:07 ` Ted Zlatanov
2009-07-21 20:43 ` Christoph Conrad
2009-07-22 15:32 ` Ted Zlatanov [this message]
2009-07-22 7:06 ` Stephen J. Turnbull
2009-07-26 17:08 ` Steinar Bang
2009-07-27 1:46 ` Stephen J. Turnbull
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=87k520n36n.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=christoph.conrad@gmx.de \
--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).