From: Richard Stallman <rms@gnu.org>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: charles@aurox.ch, emacs-devel@gnu.org
Subject: Re: Please help get ready for proofreading of Emacs manual
Date: Wed, 20 Sep 2017 16:35:43 -0400 [thread overview]
Message-ID: <E1dulih-0001iO-LH@fencepost.gnu.org> (raw)
In-Reply-To: <87377i10dr.fsf@jane> (message from Marcin Borkowski on Wed, 20 Sep 2017 06:04:32 +0200)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> > When it is a simple change, a diff is fine. You could send it as a
> > bug report. I recommend sending only 5 such simple changes in one bug
> > report -- then start another. It's only a matter of the maintainers'
> > convenience.
> How about a commit on some specialized branch?
It is for the Emacs maintainers to decide whether that method is ok.
They are the ones who will need to use it.
--
Dr Richard Stallman
President, Free Software Foundation (gnu.org, fsf.org)
Internet Hall-of-Famer (internethalloffame.org)
Skype: No way! See stallman.org/skype.html.
next prev parent reply other threads:[~2017-09-20 20:35 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 [this message]
2017-09-20 22:03 ` John Wiegley
2017-09-21 7:59 ` Eli Zaretskii
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=E1dulih-0001iO-LH@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=charles@aurox.ch \
--cc=emacs-devel@gnu.org \
--cc=mbork@mbork.pl \
/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.