From: Drew Adams <drew.adams@oracle.com>
To: bruce.connor.am@gmail.com, Karl Fogel <kfogel@red-bean.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel <emacs-devel@gnu.org>
Subject: RE: GIT mirror of Lisp dev sources [was: Char-folding: how can we implement matching...]
Date: Tue, 1 Dec 2015 13:18:01 -0800 (PST) [thread overview]
Message-ID: <0239bc4e-2682-4d73-a8ba-c5030c9fd28e@default> (raw)
In-Reply-To: <CAAdUY-KRgCMZXo6wf8FX-2Ka1YhdaAW-asRJfq5jNNi70pXQrQ@mail.gmail.com>
> > > (Why doesn't master hold the latest developments, just as
> > > (IIUC) it has always done in the past?)
> >
> > During release stabilization, at least in recent releases that
> > I can remember, the maintainers have asked that changes go to
> > the release branch first and then get ported to 'master' later.
>
> Except for new features, that is. The emacs-25 branch is for
> refining what will get release. The master branch is still
> the place where we add brand new stuff.
This is a new feature, is it not? Are we supposed to look to
`master' only for an initial implementation of a new feature,
and then look to an `emacs-N' branch for its post-branching
improvement?
next prev parent reply other threads:[~2015-12-01 21:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 15:54 Char-folding: how can we implement matching multiple characters as a single "thing"? Artur Malabarba
2015-11-30 16:12 ` Paul Eggert
2015-11-30 16:49 ` Clément Pit--Claudel
2015-11-30 17:55 ` Eli Zaretskii
2015-11-30 21:48 ` John Wiegley
2015-12-01 14:18 ` Artur Malabarba
2015-12-01 15:50 ` Eli Zaretskii
2015-12-01 16:31 ` GIT mirror of Lisp dev sources [was: Char-folding: how can we implement matching...] Drew Adams
2015-12-01 16:43 ` Steinar Bang
2015-12-01 17:14 ` Drew Adams
2015-12-01 17:32 ` Artur Malabarba
2015-12-01 18:03 ` Drew Adams
2015-12-01 18:29 ` Karl Fogel
2015-12-01 18:52 ` Artur Malabarba
2015-12-01 21:18 ` Drew Adams [this message]
2015-12-01 23:37 ` Artur Malabarba
2015-12-02 0:14 ` Drew Adams
2015-12-02 0:59 ` Artur Malabarba
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=0239bc4e-2682-4d73-a8ba-c5030c9fd28e@default \
--to=drew.adams@oracle.com \
--cc=bruce.connor.am@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kfogel@red-bean.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.
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).