From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Cc: emacs-devel@gnu.org
Subject: Re: Gnus branches and sync with Emacs
Date: Tue, 21 Jul 2009 11:09:18 -0500 [thread overview]
Message-ID: <87zlayf26p.fsf@lifelogs.com> (raw)
In-Reply-To: 87eisbw0gf.fsf@marauder.physik.uni-ulm.de
On Mon, 20 Jul 2009 22:42:24 +0200 Reiner Steib <reinersteib+gmane@imap.cc> wrote:
RS> Personally, I could live with such an arrangement, since i didn't have
RS> much time for Gnus development recently. But I also don't see much
RS> problem to have two branches (like we did with v5-10 for quite a long
RS> time) if other Gnus developers wish to commit new (potentially
RS> destabilizing) features sooner - I seem to recall that we deferred
RS> some contributions during the last months. Opinions?
I hope the bzr repository, when available, will make all this easier.
My preference is to have a place, either Gnus trunk or a branch, where I
can commit new code without waiting for approval. 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, so Gnus developers are not affecting Emacs
developers and vice versa. Then the burden falls on Reiner or others to
backport things into the "for Emacs" branch when appropriate.
This would bring the Gnus CVS trunk back to the "bleeding edge" status
it had in the past.
Ted
next prev parent reply other threads:[~2009-07-21 16:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2k534bghy.fsf@gwdg-mac-engster.top.gwdg.de>
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 [this message]
2009-07-21 17:27 ` Reiner Steib
2009-07-21 20:07 ` 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=87zlayf26p.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.