From: Eli Zaretskii <eliz@gnu.org>
To: John Wiegley <jwiegley@gmail.com>
Cc: charles@aurox.ch, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Please help get ready for proofreading of Emacs manual
Date: Thu, 21 Sep 2017 10:59:39 +0300 [thread overview]
Message-ID: <83377gfpn8.fsf@gnu.org> (raw)
In-Reply-To: <m27ewtdo3k.fsf@newartisans.com> (message from John Wiegley on Wed, 20 Sep 2017 15:03:43 -0700)
> From: John Wiegley <jwiegley@gmail.com>
> Date: Wed, 20 Sep 2017 15:03:43 -0700
> Cc: charles@aurox.ch, emacs-devel@gnu.org
>
> >>>>> "RS" == Richard Stallman <rms@gnu.org> writes:
>
> >> How about a commit on some specialized branch?
> RS> It is for the Emacs maintainers to decide whether that method is ok. They
> RS> are the ones who will need to use it.
>
> I think having a branch devoted to manual edits is a good idea, something
> branched off of emacs-26 that we can frequently merge back.
Please don't. Each additional branch brings some overhead to work
with it, and also a non-negligible probability of making mistakes,
like pushing to the wrong branch. Separate branches are justified for
experimental code changes, because they avoid breaking the main
branches which many people follow. But documentation can never break
anything, and any non-trivial changes in it need to be reviewed
anyway. So I see no need for a branch, it would just be an
unnecessary nuisance and source of errors.
Proposed changes for the manuals should be posted in the usual manner:
with "M-x report-emacs-bug RET".
TIA
next prev parent reply other threads:[~2017-09-21 7:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-17 0:00 Please help get ready for proofreading of Emacs manual Richard Stallman
2017-09-18 18:53 ` Charles A. Roelli
2017-09-18 20:10 ` Marcin Borkowski
2017-09-19 19:33 ` Richard Stallman
2017-09-20 4:04 ` Marcin Borkowski
2017-09-20 20:35 ` Richard Stallman
2017-09-20 22:03 ` John Wiegley
2017-09-21 7:59 ` Eli Zaretskii [this message]
2017-09-21 14:26 ` John Wiegley
2017-09-18 20:27 ` Eric Abrahamsen
2017-09-18 23:36 ` Nick Helm
2017-09-19 3:56 ` Eli Zaretskii
2017-09-19 7:25 ` Petteri Hintsanen
2017-09-19 19:33 ` Richard Stallman
2017-09-20 18:50 ` Charles A. Roelli
2017-09-21 18:26 ` Richard Stallman
2017-09-19 19:33 ` Richard Stallman
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=83377gfpn8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=charles@aurox.ch \
--cc=emacs-devel@gnu.org \
--cc=jwiegley@gmail.com \
--cc=rms@gnu.org \
/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.