From: Stephen Warren <swarren@wwwdotorg.org>
To: Johannes Sixt <j6t@kdbg.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Madhavan Srinivasan <maddy@linux.vnet.ibm.com>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <rob.herring@calxeda.com>,
devicetree@vger.kernel.org, git@vger.kernel.org,
steven.hill@imgtec.com, mmarek@suse.cz, swarren@nvidia.com,
linux-mips@linux-mips.org, linux-kbuild@vger.kernel.org,
james.hogan@imgtec.com
Subject: Re: git issue / [PATCH] MIPS: fix invalid symbolic link file
Date: Thu, 19 Sep 2013 14:36:47 -0600 [thread overview]
Message-ID: <523B605F.8090402@wwwdotorg.org> (raw)
In-Reply-To: <523B555E.2070508@kdbg.org>
On 09/19/2013 01:49 PM, Johannes Sixt wrote:
> Am 19.09.2013 15:39, schrieb Ralf Baechle:
>> The original patch that introduced the symlink with the \n is kernel
>> commit 3b29aa5ba204c62b3ec8f9f5b1ebd6e5d74f75d3 and is archived in
>> patchwork at http://patchwork.linux-mips.org/patch/5745/ The patch
>> file contains a \n at the end - but one would expect that from a
>> patch file that has been transfered via email, so I'm not sure how this
>> is supposed to work with emailed patches?!?
>
> The mbox file I downloaded from this link looks like this:
...
> but it should look like this:
...
> Whoever or whatever moved the '\ No newline at end of file' line above
> the patch text is to blame.
That sounds like a patchwork problem; the original copy of the message I
received looks correct.
next prev parent reply other threads:[~2013-09-19 20:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 13:09 [PATCH] MIPS: fix invalid symbolic link file Madhavan Srinivasan
2013-09-19 13:39 ` git issue / " Ralf Baechle
2013-09-19 16:37 ` Junio C Hamano
2013-09-19 19:49 ` Johannes Sixt
2013-09-19 20:36 ` Stephen Warren [this message]
2013-09-19 14:21 ` Sergei Shtylyov
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=523B605F.8090402@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=devicetree@vger.kernel.org \
--cc=git@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=j6t@kdbg.org \
--cc=james.hogan@imgtec.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=maddy@linux.vnet.ibm.com \
--cc=mmarek@suse.cz \
--cc=ralf@linux-mips.org \
--cc=rob.herring@calxeda.com \
--cc=steven.hill@imgtec.com \
--cc=swarren@nvidia.com \
/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