From: Davis Herring <herring@lanl.gov>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Karl Fogel <kfogel@red-bean.com>,
Drew Adams <drew.adams@oracle.com>,
emacs-devel@gnu.org
Subject: Re: Question about intended behavior of 'insert-for-yank-1'.
Date: Tue, 4 Oct 2016 14:16:58 -0600 [thread overview]
Message-ID: <9eae5d28-92d7-e0f8-8002-6e74f2dd84a4@lanl.gov> (raw)
In-Reply-To: <837f9om0yt.fsf@gnu.org>
>>> You need to understand the logic behind the instructions in
>>> CONTRIBUTE: the release branch should only get fixes that are either
>>> necessary, or are safe, i.e. cannot possibly break the release. And
>>> doc changes obviously belong to this latter class.
>>
>> I understand that logic. However, do you mean s/only/always/ above?
>
> I don't see the difference. "Only" means "always" in this case.
The two possible meanings are "the release branch should get only
fixes..." or "only the release branch should get fixes" (which is
equivalent to "the release branch should get all fixes").
Of course, both can be true (iff).
Davis
--
This product is sold by volume, not by mass. If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.
next prev parent reply other threads:[~2016-10-04 20:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 5:17 Question about intended behavior of 'insert-for-yank-1' Karl Fogel
2016-09-12 16:59 ` Eli Zaretskii
2016-09-12 17:15 ` Karl Fogel
2016-09-12 18:32 ` Eli Zaretskii
2016-09-12 22:36 ` Karl Fogel
2016-09-12 22:54 ` Drew Adams
2016-09-12 23:08 ` Karl Fogel
2016-10-03 0:53 ` Karl Fogel
2016-10-03 3:17 ` Noam Postavsky
2016-10-03 6:53 ` Eli Zaretskii
2016-10-03 19:21 ` Karl Fogel
2016-10-03 6:44 ` Eli Zaretskii
2016-10-03 19:17 ` Karl Fogel
2016-10-04 6:03 ` Eli Zaretskii
2016-10-04 17:40 ` Karl Fogel
2016-10-04 18:19 ` Eli Zaretskii
2016-10-04 20:16 ` Davis Herring [this message]
2016-10-04 21:04 ` Karl Fogel
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=9eae5d28-92d7-e0f8-8002-6e74f2dd84a4@lanl.gov \
--to=herring@lanl.gov \
--cc=drew.adams@oracle.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 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.