* Should fixes for Bug#23936 go also to emacs-25?
@ 2016-07-21 9:04 Tino Calancha
2016-07-21 10:12 ` Paul Eggert
2016-07-21 14:31 ` Eli Zaretskii
0 siblings, 2 replies; 5+ messages in thread
From: Tino Calancha @ 2016-07-21 9:04 UTC (permalink / raw)
To: emacs-devel
Bug#23936 fix several wrong sentences in shell-command,
shell-command-on-region
doc strings.
After pushing the fix to the master branch Noam reminds me that such
kind of fixes should go to the release branch.
Today i found another wrong sentence in same doc strings
(i didn't push the fix for this new issue). It seems i sent email
twice to Bug#23936 due to connectivity problems. Sorry.
May i ask you what is the procedure here? What branches should get the fix?
Thank you
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Should fixes for Bug#23936 go also to emacs-25?
2016-07-21 9:04 Should fixes for Bug#23936 go also to emacs-25? Tino Calancha
@ 2016-07-21 10:12 ` Paul Eggert
2016-07-21 14:31 ` Eli Zaretskii
1 sibling, 0 replies; 5+ messages in thread
From: Paul Eggert @ 2016-07-21 10:12 UTC (permalink / raw)
To: Tino Calancha, emacs-devel
On 07/21/2016 11:04 AM, Tino Calancha wrote:
> What branches should get the fix?
If it's purely fixes for documentation that describes emacs-25 behavior,
it should go into emacs-25. That being said, we don't want to add major
new constraints to the Emacs 25 documentation, so that we can preserve
wiggle room for later releases.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Should fixes for Bug#23936 go also to emacs-25?
2016-07-21 9:04 Should fixes for Bug#23936 go also to emacs-25? Tino Calancha
2016-07-21 10:12 ` Paul Eggert
@ 2016-07-21 14:31 ` Eli Zaretskii
2016-07-21 15:01 ` Tino Calancha
1 sibling, 1 reply; 5+ messages in thread
From: Eli Zaretskii @ 2016-07-21 14:31 UTC (permalink / raw)
To: Tino Calancha; +Cc: emacs-devel
> From: Tino Calancha <tino.calancha@gmail.com>
> Date: Thu, 21 Jul 2016 18:04:06 +0900 (JST)
>
> May i ask you what is the procedure here? What branches should get the fix?
Documentation fixes that are relevant to the behavior on emacs-25
should be pushed to emacs-25.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Should fixes for Bug#23936 go also to emacs-25?
2016-07-21 14:31 ` Eli Zaretskii
@ 2016-07-21 15:01 ` Tino Calancha
2016-07-21 15:14 ` Eli Zaretskii
0 siblings, 1 reply; 5+ messages in thread
From: Tino Calancha @ 2016-07-21 15:01 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: emacs-devel, Tino Calancha
On Thu, 21 Jul 2016, Eli Zaretskii wrote:
>> From: Tino Calancha <tino.calancha@gmail.com>
>> Date: Thu, 21 Jul 2016 18:04:06 +0900 (JST)
>>
>> May i ask you what is the procedure here? What branches should get the fix?
>
> Documentation fixes that are relevant to the behavior on emacs-25
> should be pushed to emacs-25.
Thank you Eli for the answer.
The doc fixes in Bug#23936 are not relevant to the behaviour
on emacs-25; they seems not urgent at all.
Regards,
Tino
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Should fixes for Bug#23936 go also to emacs-25?
2016-07-21 15:01 ` Tino Calancha
@ 2016-07-21 15:14 ` Eli Zaretskii
0 siblings, 0 replies; 5+ messages in thread
From: Eli Zaretskii @ 2016-07-21 15:14 UTC (permalink / raw)
To: Tino Calancha; +Cc: emacs-devel
> From: Tino Calancha <tino.calancha@gmail.com>
> Date: Fri, 22 Jul 2016 00:01:03 +0900 (JST)
> cc: Tino Calancha <tino.calancha@gmail.com>, emacs-devel@gnu.org
>
> > Documentation fixes that are relevant to the behavior on emacs-25
> > should be pushed to emacs-25.
> Thank you Eli for the answer.
> The doc fixes in Bug#23936 are not relevant to the behaviour
> on emacs-25; they seems not urgent at all.
Urgency is not an issue when documentation fixes are concerned. What
matters is whether the changes make the documentation better. Of
course, if the behavior whose description you want to improve/correct
is only available on master, then the change shouldn't be pushed to
emacs-25.
Thanks.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2016-07-21 15:14 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-07-21 9:04 Should fixes for Bug#23936 go also to emacs-25? Tino Calancha
2016-07-21 10:12 ` Paul Eggert
2016-07-21 14:31 ` Eli Zaretskii
2016-07-21 15:01 ` Tino Calancha
2016-07-21 15:14 ` Eli Zaretskii
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).