unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Steinar Bang <sb@dod.no>
To: emacs-devel@gnu.org
Cc: ding@gnus.org
Subject: Re: Gnus branches and sync with Emacs
Date: Sun, 26 Jul 2009 19:08:42 +0200	[thread overview]
Message-ID: <m3eis3cqxx.fsf@dod.no> (raw)
In-Reply-To: 878wihgpsl.fsf@uwakimon.sk.tsukuba.ac.jp

>>>>> "Stephen J. Turnbull" <stephen@xemacs.org>:

> What the bzr repo will make definitely *much* easier *immediately* is
> for you to keep your own bleeding edge branch locally, and then push
> from there to the Gnus mainline when it's "open for commits".  You'll
> need to learn more of bzr than you might otherwise, but it's worth it.

FWIW I have been using the Gnus trunk for over ten years now (closing on
twelve, I think), and except for when lars were rolling releases, there
has never been a time with bleeding edge work hasn't been ok to do on
the trunk.

If you are going to do big changes, it's much better to let them loose
on a bunch of testers as early as possible, instead of sitting with them
on a branch just testing them yourself, and then committing them
big-bang to the trunk.







  reply	other threads:[~2009-07-26 17:08 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
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 [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3eis3cqxx.fsf@dod.no \
    --to=sb@dod.no \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).