From: Glenn Morris <rgm@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org, Dmitry Dzhus <dima@sphinx.net.ru>,
Miles Bader <miles@gnu.org>
Subject: Re: New sync'd branch
Date: Thu, 27 Aug 2009 17:52:02 -0400 [thread overview]
Message-ID: <rd63c8q60t.fsf@fencepost.gnu.org> (raw)
In-Reply-To: jwvprai76a5.fsf-monnier+emacs@gnu.org
Stefan Monnier wrote:
> So I believe we should create a new branch EMACS_23 which will play the
> role currently played by the trunk, so the trunk can now be open to more
> experimental development (bidi, cpp->autoconf conversion, lexbind, ...),
> targetted for Emacs-24.
It would be good to always have a place for such experimental things.
What's the reason to have two branches EMACS_23 and EMACS_23_1_RC?
The latter will be almost entirely unused. Are you holding it in
reserve in case 23.2 is needed at short notice, eg for a security issue?
> There are some problem with this:
> - Changes on the 23 branch need to be sync'd to the trunk. As long as
> we haven't switched to Bzr, that means we need Miles to do the sync
> for us.
Or we sync manually, or someone else volunteers to do it "automatically".
> - The 23 branch will not see as much testing any more.
I think that's the biggest issue.
[milesomatic merging]
> You don't seem too enthusiastic. Maybe another option would be to
> make the Emacs-24 branch not in CVS but directly in Git (from where it
> will be eventually turned into a Bzr branch).
Sorry, but that's an idea I have no enthusiasm for.
I'm happy to sync my own changes manually between CVS branches, or
wait for Bzr (assuming this solves all problems).
next prev parent reply other threads:[~2009-08-27 21:52 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-23 22:21 New sync'd branch Stefan Monnier
2009-08-23 22:35 ` joakim
2009-08-24 13:58 ` Leo
2009-08-24 19:24 ` Dmitry Dzhus
2009-08-25 17:44 ` Stefan Monnier
2009-08-26 8:31 ` Miles Bader
2009-08-26 19:04 ` Stefan Monnier
2009-08-27 3:09 ` Eli Zaretskii
2009-08-27 4:47 ` Miles Bader
2009-08-27 5:38 ` Teemu Likonen
2009-08-28 8:34 ` Eli Zaretskii
2009-08-27 6:33 ` Ken Raeburn
2009-08-27 7:08 ` Teemu Likonen
2009-08-27 7:14 ` Christian Faulhammer
2009-08-27 8:55 ` Ken Raeburn
2009-08-27 9:07 ` Miles Bader
2009-08-27 10:11 ` Stephen J. Turnbull
2009-08-28 9:18 ` Eli Zaretskii
2009-08-27 9:47 ` joakim
2009-08-28 9:04 ` Eli Zaretskii
2009-08-28 9:12 ` Miles Bader
2009-08-28 9:19 ` Teemu Likonen
2009-08-28 9:32 ` Eli Zaretskii
2009-08-28 13:03 ` David Kastrup
2009-08-28 13:46 ` Óscar Fuentes
2009-08-28 14:55 ` Juanma Barranquero
2009-08-28 17:11 ` Óscar Fuentes
2009-08-28 17:49 ` Juanma Barranquero
2009-08-28 18:00 ` David Reitter
2009-08-29 3:56 ` Stephen J. Turnbull
2009-08-29 20:20 ` Richard Stallman
2009-08-28 15:08 ` David Kastrup
2009-08-28 17:21 ` Óscar Fuentes
2009-08-28 19:33 ` David Kastrup
2009-08-28 21:41 ` Óscar Fuentes
2009-08-28 22:20 ` Miles Bader
2009-08-28 22:55 ` Óscar Fuentes
2009-08-29 0:17 ` Miles Bader
2009-08-29 9:08 ` David Kastrup
2009-08-29 15:25 ` Stefan Monnier
2009-08-29 0:46 ` Stefan Monnier
2009-08-28 22:00 ` Miles Bader
2009-08-28 14:01 ` Juanma Barranquero
2009-08-28 14:08 ` Eli Zaretskii
2009-08-28 14:13 ` Juanma Barranquero
2009-08-28 14:33 ` Eli Zaretskii
2009-08-28 14:44 ` Juanma Barranquero
2009-08-28 9:38 ` joakim
2009-08-28 9:48 ` Eli Zaretskii
2009-08-28 10:02 ` Eli Zaretskii
2009-08-28 11:18 ` David Kastrup
2009-08-28 15:59 ` David Reitter
2009-08-27 21:27 ` Stefan Monnier
2009-08-28 8:28 ` Eli Zaretskii
2009-08-27 21:52 ` Glenn Morris [this message]
2009-08-27 22:17 ` Chong Yidong
-- strict thread matches above, loose matches on Subject: below --
2009-08-24 22:25 Nick Roberts
2009-08-25 9:29 ` joakim
2009-08-25 14:06 ` Chong Yidong
2009-08-25 21:02 ` Nick Roberts
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=rd63c8q60t.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=dima@sphinx.net.ru \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.