From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Subject: Re: [PULL] Documentation for 5.5
Date: Mon, 2 Dec 2019 01:19:28 +0100 [thread overview]
Message-ID: <20191202001928.GA4146@latitude> (raw)
In-Reply-To: <20191130171428.6c09f892@lwn.net>
[-- Attachment #1: Type: text/plain, Size: 880 bytes --]
On Sat, Nov 30, 2019 at 05:14:28PM -0700, Jonathan Corbet wrote:
[...]
> All of the afflicted files arrived in that state as the result of a pair
> of patches from Jonathan (copied); I have verified that the original
> patches also had the DOS line endings.
Not sure why, or where in the mails' path this happened, but the base64
with CR/LF inside is also present in the copies that went directly to
me, rather than via the mailing lists.
> Anyway, if I revert the two offending patches and resend the pull, is that
> good enough, or do you want this mess out of the history entirely?
On a somewhat related note: "Documentation: networking: device drivers:
Remove stray asterisks" was also picked up via the networking tree.
Perhaps I should have mentioned that when I became aware(?)
> Sorry for the trouble,
Well, same here :/
Jonathan Neuschäfer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-12-02 0:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 16:30 [PULL] Documentation for 5.5 Jonathan Corbet
2019-11-30 23:11 ` Linus Torvalds
2019-12-01 0:14 ` Jonathan Corbet
2019-12-01 0:40 ` Linus Torvalds
2019-12-02 0:19 ` Jonathan Neuschäfer [this message]
2019-12-02 14:29 ` Jonathan Corbet
2019-12-02 21:05 ` pr-tracker-bot
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=20191202001928.GA4146@latitude \
--to=j.neuschaefer@gmx.net \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).