From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Cc: ding@gnus.org
Subject: Re: Gnus branches and sync with Emacs
Date: Mon, 20 Jul 2009 12:23:08 -0500 [thread overview]
Message-ID: <87skgri803.fsf@lifelogs.com> (raw)
In-Reply-To: <87eisdn3ng.fsf@marauder.physik.uni-ulm.de>
On Sat, 18 Jul 2009 22:21:23 +0200 Reiner Steib <reinersteib+gmane@imap.cc> wrote:
RS> If Gnus developers want to start adding new features to Gnus CVS now,
RS> we also need to have a bug-fix-only Gnus branch as well, say "v5-12",
RS> which is synced with Emacs trunk (to be Emacs 23.2). v5-12 would also
RS> be used for future Gnus 5.12.* releases.
RS> As there's no Emacs branch (or trunk) for new features, this would
RS> imply that we cannot sync Gnus to Emacs for quite some time (dunno how
RS> are the plans for the next major version of Emacs).
First of all, sorry for my commit. I had assumed that since Emacs got
branched and the trunk was open, it was OK to commit into the Gnus trunk
as well. I did not check with you and I should have.
Please let me know when I can resume comitting to the Gnus CVS trunk.
Ted
next prev parent reply other threads:[~2009-07-20 17:23 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 ` Ted Zlatanov [this message]
2009-07-20 18:18 ` Gnus branches and sync with Emacs 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
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=87skgri803.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.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).