From: nbraud <nbraud@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] Fix typo in NEWS
Date: Mon, 02 Nov 2020 09:58:32 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-190@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 286 bytes --]
There is a new pull request by nbraud against master on the mblaze repository
https://github.com/nbraud/mblaze changelog-typo
https://github.com/leahneukirchen/mblaze/pull/190
Fix typo in NEWS
None
A patch file from https://github.com/leahneukirchen/mblaze/pull/190.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-changelog-typo-190.patch --]
[-- Type: text/x-diff, Size: 839 bytes --]
From bac0aa7b6a192b349179ceb1ba9e285caa951eac Mon Sep 17 00:00:00 2001
From: nicoo <nicoo@debian.org>
Date: Mon, 2 Nov 2020 09:52:02 +0100
Subject: [PATCH] Fix typo in NEWS
---
NEWS.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/NEWS.md b/NEWS.md
index b5a85b7..396d9aa 100644
--- a/NEWS.md
+++ b/NEWS.md
@@ -2,8 +2,8 @@
* Caution! Backwards incompatible changes:
* As a message name, `-` now refers to the message on the standard input,
- and not the the previous message anymore. Use `.-` to refer to
- the previous message in a short way.
+ and not the previous message anymore. Use `.-` to refer to the previous
+ message in a short way.
The tools will print a warning if you use `-` and the standard input
comes from a TTY.
* mpick: use the -F flag to read script files.
next reply other threads:[~2020-11-02 8:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 8:58 nbraud [this message]
2020-11-02 9:03 ` [PR PATCH] [Closed]: " leahneukirchen
2021-01-14 16:05 [PR PATCH] " nbraud
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=gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-190@inbox.vuxu.org \
--to=nbraud@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).