From: Ralf Baechle <ralf@linux-mips.org>
To: 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
Cc: 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 15:39:20 +0200 [thread overview]
Message-ID: <20130919133920.GA22468@linux-mips.org> (raw)
In-Reply-To: <1379596148-32520-1-git-send-email-maddy@linux.vnet.ibm.com>
On Thu, Sep 19, 2013 at 06:39:08PM +0530, Madhavan Srinivasan wrote:
(Git folks, please read on.)
> Commit 3b29aa5ba204c created a symlink file in include/dt-bindings.
> Even though commit diff is fine, symlink is invalid.
> ls -lb shows a newline character at the end of the filename.
>
> lrwxrwxrwx 1 maddy maddy 35 Sep 19 18:11 dt-bindings ->
> ../../../../../include/dt-bindings\n
>
> Signed-off-by: Madhavan Srinivasan <maddy@linux.vnet.ibm.com>
> ---
> arch/mips/boot/dts/include/dt-bindings | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/mips/boot/dts/include/dt-bindings b/arch/mips/boot/dts/include/dt-bindings
> index 68ae388..08c00e4 120000
> --- a/arch/mips/boot/dts/include/dt-bindings
> +++ b/arch/mips/boot/dts/include/dt-bindings
> @@ -1 +1 @@
> -../../../../../include/dt-bindings
> +../../../../../include/dt-bindings
> \ No newline at end of file
> --
> 1.7.10.4
I applied your patch - but now git-show shows it as an empty commit and
ls -lb arch/mips/boot/dts/include/dt-bindings
still shows the \n at the end of the link target. Things are looking ok
now that I manually fixed the link and commited the result. I hope
git-push and git-pull are going to handle this correct.
So, I wonder if this is a git bug.
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?!?
Anyway, I'm not too fond of sylinks in the tree or in patches and I'm
wondering if we could get rid of them for something more bullet proof.
Ralf
next parent reply other threads:[~2013-09-19 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1379596148-32520-1-git-send-email-maddy@linux.vnet.ibm.com>
2013-09-19 13:39 ` Ralf Baechle [this message]
[not found] ` <20130919133920.GA22468-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org>
2013-09-19 16:37 ` git issue / [PATCH] MIPS: fix invalid symbolic link file Junio C Hamano
2013-09-19 19:49 ` Johannes Sixt
2013-09-19 20:36 ` Stephen Warren
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=20130919133920.GA22468@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=devicetree@vger.kernel.org \
--cc=git@vger.kernel.org \
--cc=grant.likely@linaro.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=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;
as well as URLs for NNTP newsgroup(s).