From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: Gnus branches and sync with Emacs
Date: Tue, 21 Jul 2009 19:27:00 +0200 [thread overview]
Message-ID: <87tz16t09n.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87zlayf26p.fsf@lifelogs.com> (Ted Zlatanov's message of "Tue, 21 Jul 2009 11:09:18 -0500")
On Tue, Jul 21 2009, Ted Zlatanov wrote:
> My preference is to have a place, either Gnus trunk or a branch, where I
> can commit new code without waiting for approval.
Noted.
> I would prefer that to be the Gnus trunk, and I think it makes sense
> to have a Gnus CVS branch for the purpose of synchronization with
> Emacs CVS. IOW, the synchronization that happens from the Gnus
> trunk right now should happen from a "for Emacs" branch,
This would be the v5-12 branch in my suggestion.
> so Gnus developers are not affecting Emacs developers and vice
> versa.
Just to clarify: The question is not _whether or not_ to sync, but
_when and how_ we sync the Gnus repository to Emacs' repository.
> Then the burden falls on Reiner or others to backport things into
> the "for Emacs" branch when appropriate.
The "burden" basically is on Miles, but it's more or less
automatically. Well, at least if every developer commits bugfixes to
the bugfix-branch (which will be synced to the development branch) by
Miles.
> This would bring the Gnus CVS trunk back to the "bleeding edge" status
> it had in the past.
The Gnus trunk also had long stabilizing periods (e.g. from 5.10.1 to
5.10.6).
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2009-07-21 17:27 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 [this message]
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=87tz16t09n.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.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).