From: John Wiegley <jwiegley@gmail.com>
To: Mark Oteiza <mvoteiza@udel.edu>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Your latest commits on emacs-25
Date: Tue, 19 Apr 2016 18:47:01 -0700 [thread overview]
Message-ID: <m2twixdpbe.fsf@newartisans.com> (raw)
In-Reply-To: <20160420012845.GA4548@holos.localdomain> (Mark Oteiza's message of "Tue, 19 Apr 2016 21:28:45 -0400")
>>>>> Mark Oteiza <mvoteiza@udel.edu> writes:
> There has been much churn over what the purpose of the branches are, the
> rationale of which was neither explained nor clarified on the relevant
> thread on which I specifically recall mentioning what the status quo was and
> asking why it was being changed. It is pretty irritating to be jumped on for
> what are perhaps the least intrusive pushes of those I have made recently.
I hope I can clarify the current purpose of our branches:
emacs-25: We're preparing this for release, so everyone should be very
cautious. Even a safe fix, if not necessary, should go to master now.
master: Work toward Emacs 26. Most changes should go here, but new API
changes and new functionality should still not be introduced without some
discussion on this list.
feature branches: Commit anything you like, for review by others on this
list.
When it comes to emacs-25, it's not that your change was improper, it's just
that a question was raised, and so it needed to be addressed.
I apologize if it sounded like you were being jumped on, that was not the
intent. It was purely out of caution for this branch -- a caution that will
continue to intensify as we approach the hopeful target of June 21.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2016-04-20 1:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-16 19:16 Your latest commits on emacs-25 Eli Zaretskii
2016-04-16 20:36 ` John Wiegley
2016-04-19 16:28 ` John Wiegley
2016-04-20 1:28 ` Mark Oteiza
2016-04-20 1:47 ` John Wiegley [this message]
2016-04-20 5:58 ` Paul Eggert
2016-04-20 14:40 ` Eli Zaretskii
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=m2twixdpbe.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mvoteiza@udel.edu \
/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.