unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: nljlistbox2@gmail.com (N. Jackson)
To: 23657@debbugs.gnu.org
Subject: bug#23657: [PATCH] 25.0.94; Typo in "Sending Patches" node of the Emacs manual
Date: Mon, 30 May 2016 11:51:18 -0300	[thread overview]
Message-ID: <87twhfwqe1.fsf@moondust.awandering> (raw)
In-Reply-To: <87y46rwqmk.fsf@moondust.awandering> (N. Jackson's message of "Mon, 30 May 2016 11:46:11 -0300")

[-- Attachment #1: Type: text/plain, Size: 199 bytes --]

At 11:46 -0300 on Monday 2016-05-30, N. Jackson wrote:

> There is a typo in the node "54.5 Sending Patches for GNU Emacs" of the
> Emacs manual (info "(emacs) Sending Patches").
>
> Patch follows.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Patch for Bug#23657 --]
[-- Type: text/x-patch, Size: 698 bytes --]

diff --git a/doc/emacs/trouble.texi b/doc/emacs/trouble.texi
index 6f6071b..ae309ae 100644
--- a/doc/emacs/trouble.texi
+++ b/doc/emacs/trouble.texi
@@ -1130,7 +1130,7 @@ Sending Patches
 Use @samp{diff -u} to make your diffs.  Diffs without context are hard
 to install reliably.  More than that, they are hard to study; we must
 always study a patch to decide whether we want to install it.  Context
-format is better than contextless diffs, but we prefer we unified format.
+format is better than contextless diffs, but we prefer the unified format.
 
 If you have GNU diff, use @samp{diff -u -F'^[_a-zA-Z0-9$]\+ *('} when
 making diffs of C code.  This shows the name of the function that each

  reply	other threads:[~2016-05-30 14:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-30 14:46 bug#23657: 25.0.94; Typo in "Sending Patches" node of the Emacs manual N. Jackson
2016-05-30 14:51 ` N. Jackson [this message]
2016-05-30 14:52 ` Dmitry Gutov
2016-05-30 21:51   ` N. Jackson
2016-05-30 21:58     ` Dmitry Gutov

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=87twhfwqe1.fsf@moondust.awandering \
    --to=nljlistbox2@gmail.com \
    --cc=23657@debbugs.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 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).