From: Jeff Garzik <jeff@garzik.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: linus.walleij@linaro.org,
Russell King <rmk+kernel@arm.linux.org.uk>,
swarren@nvidia.com, Olof Johansson <olof@lixom.net>,
Ben Hutchings <ben@decadent.org.uk>,
"Arnaud Patard (Rtp)" <arnaud.patard@rtp-net.org>,
Grant Likely <grant.likely@secretlab.ca>,
Wolfram Sang <w.sang@pengutronix.de>,
bs14@csr.com
Subject: Zero-length ARM headers in git HEAD
Date: Fri, 28 Oct 2011 15:50:10 -0400 [thread overview]
Message-ID: <4EAB0772.40404@garzik.org> (raw)
Gents,
In the following kernel commits,
9c587c05d715ca8461342c2cb3b4a67036b5c22b
ea5abbd215b749b2ff14397a47a5e65741c67bf4
cc890cd78acd7ab03442907d354b6af34e973cb3
the file ...$platform/mach/gpio.h is replaced with an empty file. This
disagrees with kernel tradition and kernel makefiles, where zero length
files are intentionally deleted when "make distclean" is executed.
As a result, git sequences such as "make distclean ; git checkout
master" may fail, because several files are present in the index but not
on disk, making it appear as if modifications have been made:
$ git checkout master
D arch/arm/mach-lpc32xx/include/mach/gpio.h
D arch/arm/mach-tegra/include/mach/gpio.h
D arch/arm/mach-u300/include/mach/gpio.h
An update, either (a) making these files non-zero length or (b) deleting
the files in git would be appreciated. Reading the commit descriptions,
it appears (a) is the correct path?
Jeff
next reply other threads:[~2011-10-28 19:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 19:50 Jeff Garzik [this message]
2011-10-28 20:09 ` Zero-length ARM headers in git HEAD Linus Walleij
2011-10-28 20:37 ` Russell King
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=4EAB0772.40404@garzik.org \
--to=jeff@garzik.org \
--cc=arnaud.patard@rtp-net.org \
--cc=ben@decadent.org.uk \
--cc=bs14@csr.com \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=swarren@nvidia.com \
--cc=w.sang@pengutronix.de \
/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