unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 34756@debbugs.gnu.org
Subject: bug#34756: 26.1.92; Minor typos across manuals
Date: Tue, 05 Mar 2019 18:17:05 +0200	[thread overview]
Message-ID: <83woldcn3y.fsf@gnu.org> (raw)
In-Reply-To: <87mum9u30u.fsf@tcd.ie> (contovob@tcd.ie)

> From: "Basil L. Contovounesios" <contovob@tcd.ie>
> Date: Tue, 05 Mar 2019 08:41:21 +0000
> 
> Are the three attached patches acceptable for the emacs-26 branch?

Documentation changes should always go to the release branch, unless
they document features only available on master.

> If so, should I add this bug number to all or none of them?

It's okay to push all of them under the same bug number, and even in a
single commit.  There's no need to distinguish between changes that
correct typos, they are all "alike" for all practical purposes.

Thanks.





  reply	other threads:[~2019-03-05 16:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-05  8:41 bug#34756: 26.1.92; Minor typos across manuals Basil L. Contovounesios
2019-03-05 16:17 ` Eli Zaretskii [this message]
2019-03-05 20:44   ` Basil L. Contovounesios
2019-03-05 20:48     ` Basil L. Contovounesios
2019-03-06 16:06       ` Eli Zaretskii
2019-03-13 17:35         ` Basil L. Contovounesios
2019-03-06  3:39     ` Eli Zaretskii
2019-03-13 17:31       ` Basil L. Contovounesios
2019-03-13 18:14         ` Eli Zaretskii
2019-03-13 21:32           ` Basil L. Contovounesios

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=83woldcn3y.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=34756@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    /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).