From: Bryan Wu <bryan.wu@analog.com>
To: Marco Roeland <marco.roeland@xs4all.nl>
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
Jeff Garzik <jeff@garzik.org>,
"Robert P. J. Day" <rpjday@mindspring.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Git Mailing List <git@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: why does git perpetually complain about include/asm-blackfin/macros.h?
Date: Tue, 03 Jul 2007 08:28:09 +0800 [thread overview]
Message-ID: <1183422489.10353.2.camel@roc-laptop> (raw)
In-Reply-To: <20070702142430.GA10400@fiberbit.xs4all.nl>
On Mon, 2007-07-02 at 16:24 +0200, Marco Roeland wrote:
> On Monday July 2nd 2007 at 15:58 Jesper Juhl wrote:
>
> > [obnoxious zero sized file include/asm-blackfin/macros.h that gets
> > zapped by toolchains and resurrected again by git]
> >
> > I've seen that as well, but in my case doing a
> > $ git reset --hard master
> > fixed it.
>
> Dangerous, as it may overwrite local changes you have! A simple "git
> checkout include/asm-blackfin/macros.h" is much safer in this case.
>
> In git commit df30b11 this file got redundant. Perhaps because a normal
> patch was applied, instead of with git, the file didn't get deleted from
> the repository but truncated to size zero. Not strictly wrong perse, but
> for the Linux repository highly unusual (and the only one at that).
>
> Your toolchain perhaps deletes files with zero size after cleaning up or
> something. Git then notices that you deleted this file.
>
> Perhaps someone can apply something like the following to finally fix
> this up:
>
> commit 7d98740800f3d9ad2428afa8c677be9573a51b7b
> Author: Marco Roeland <marco.roeland@xs4all.nl>
> Date: Mon Jul 2 16:19:49 2007 +0200
>
> Blackfin arch: remove zero-sized include/asm-blackfin/macros.h
>
> This file accidentally got truncated instead of deleted in commit df30b11.
>
> Signed-off-by: Marco Roeland <marco.roeland@xs4all.nl>
>
> diff --git a/include/asm-blackfin/macros.h b/include/asm-blackfin/macros.h
> deleted file mode 100644
> index e69de29..0000000
> -
Thanks, Applied to the blackfin-2.6.git tree for Linus pull.
- Bryan
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-07-03 0:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0707020800010.1972@localhost.localdomain>
2007-07-02 12:29 ` why does git perpetually complain about include/asm-blackfin/macros.h? Jeff Garzik
2007-07-02 13:58 ` Jesper Juhl
2007-07-02 14:10 ` Jeff Garzik
2007-07-02 14:22 ` Robert P. J. Day
2007-07-02 14:22 ` Alex Riesen
2007-07-02 14:25 ` Alex Riesen
2007-07-02 14:29 ` Marco Roeland
2007-07-02 15:09 ` [PATCH] Blackfin arch: include/asm-blackfin/macros.h die die die Marco Roeland
2007-07-03 0:39 ` Bryan Wu
2007-07-02 14:37 ` why does git perpetually complain about include/asm-blackfin/macros.h? Jeff Garzik
2007-07-14 7:45 ` Sam Ravnborg
2007-07-02 14:24 ` Marco Roeland
2007-07-03 0:28 ` Bryan Wu [this message]
2007-07-02 15:36 ` Linus Torvalds
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=1183422489.10353.2.camel@roc-laptop \
--to=bryan.wu@analog.com \
--cc=git@vger.kernel.org \
--cc=jeff@garzik.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.roeland@xs4all.nl \
--cc=rpjday@mindspring.com \
--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).