From: Eli Zaretskii <eliz@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: ofv@wanadoo.es, emacs-devel@gnu.org
Subject: Re: New branch
Date: Thu, 28 Jan 2010 23:08:52 +0200 [thread overview]
Message-ID: <837hr2szrv.fsf@gnu.org> (raw)
In-Reply-To: <87mxzyvvip.fsf@stupidchicken.com>
> From: Chong Yidong <cyd@stupidchicken.com>
> Date: Thu, 28 Jan 2010 15:12:30 -0500
> Cc: emacs-devel@gnu.org
>
> Óscar Fuentes <ofv@wanadoo.es> writes:
>
> > This is correct. But you have to think too about the branches out there
> > that are pointing to upstream branches...
>
> Yes, and the idea is to use trunk as a signal for development
> priorities. Right now, we want the focus to be on fixing bugs, so the
> Emacs 23.2 code is on trunk. The `pending' branch is for those few who
> are looking ahead to Emacs 24, but we don't want that to encourage that
> for the bulk of developers, yet.
But the disadvantages pointed out by Óscar of changing the semantics
of trunk, pending, and other non-specific names, are real. So I'd
really prefer that we use a special branch for releasing 23.2, leaving
the trunk for future versions, because then the semantics of trunk
would not change under our feet one day.
next prev parent reply other threads:[~2010-01-28 21:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 2:37 New branch Stefan Monnier
2010-01-28 5:40 ` Eli Zaretskii
2010-01-28 19:13 ` Stefan Monnier
2010-01-28 19:41 ` Óscar Fuentes
2010-01-28 20:12 ` Chong Yidong
2010-01-28 21:08 ` Eli Zaretskii [this message]
2010-01-28 22:53 ` Stefan Monnier
2010-01-28 23:22 ` Óscar Fuentes
2010-01-29 1:55 ` Stefan Monnier
2010-01-29 4:24 ` Stephen J. Turnbull
2010-01-29 5:13 ` Stefan Monnier
2010-02-03 1:05 ` Kenichi Handa
2010-02-03 2:31 ` Stefan Monnier
2010-02-03 4:24 ` Kenichi Handa
2010-02-03 14:20 ` Stefan Monnier
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=837hr2szrv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.es \
/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).