unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: guix-devel@gnu.org
Subject: [PATCH] doc: Fix "could could" typo in Submitting Patches section
Date: Wed, 14 Dec 2016 09:38:36 -0800	[thread overview]
Message-ID: <87k2b2fm1v.fsf@gmail.com> (raw)

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

Hi Guix!

Please receive this trivial patch (attached) for the Guix info manual.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Fix "could could" typo in Submitting Patches section --]
[-- Type: text/x-patch, Size: 932 bytes --]

From 805165a6114f745a2e9713215f9935ff78437c49 Mon Sep 17 00:00:00 2001
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Date: Wed, 14 Dec 2016 09:30:17 -0800
Subject: [PATCH] doc: Fix "could could" typo in Submitting Patches section

* doc/contributing.texi (Submitting Patches): s/could could/could /
---
 doc/contributing.texi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/contributing.texi b/doc/contributing.texi
index 18d891db4..de08f9b35 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -368,4 +368,4 @@ a subject.  You may use your email client or the @command{git
 send-email} command.  We prefer to get patches in plain text messages,
 either inline or as MIME attachments.  You are advised to pay attention if
 your email client changes anything like line breaks or indentation which
-could could potentially break the patches.
+could potentially break the patches.
-- 
2.11.0


[-- Attachment #3: Type: text/plain, Size: 7 bytes --]


Maxim

             reply	other threads:[~2016-12-14 17:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-14 17:38 Maxim Cournoyer [this message]
2016-12-14 19:58 ` [PATCH] doc: Fix "could could" typo in Submitting Patches section Leo Famulari

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k2b2fm1v.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=guix-devel@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/guix.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).