From: Sam Ravnborg <sam@ravnborg.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: Alex Riesen <raa.lkml@gmail.com>,
Jesper Juhl <jesper.juhl@gmail.com>,
"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: Sat, 14 Jul 2007 09:45:58 +0200 [thread overview]
Message-ID: <20070714074558.GA8047@uranus.ravnborg.org> (raw)
In-Reply-To: <46890DA8.4070400@garzik.org>
On Mon, Jul 02, 2007 at 10:37:28AM -0400, Jeff Garzik wrote:
> Alex Riesen wrote:
> >Do some of your branches miss the commit by which it was removed?
>
> git-clone followed by git-checkout master recreates the problem.
>
> But to answer your question directly, I rebase, so they absolutely do
> not miss any commits.
>
>
> >It is somewhat unclear what "reappear" means, though: do you mean
>
> Attempts to give you precise output to answer your question yielded a
> data point, the kernel's "make distclean" causes this:
>
> [jgarzik@pretzel linux-2.6]$ make distclean && git checkout master &&
> git diff HEAD
> D include/asm-blackfin/macros.h
> Switched to branch "master"
> diff --git a/include/asm-blackfin/macros.h b/include/asm-blackfin/macros.h
> deleted file mode 100644
> index e69de29..0000000
>
> [jgarzik@pretzel linux-2.6]$ git checkout -f
>
> [jgarzik@pretzel linux-2.6]$ make distclean && git checkout master &&
> git diff HEAD
> D include/asm-blackfin/macros.h
> Switched to branch "master"
> diff --git a/include/asm-blackfin/macros.h b/include/asm-blackfin/macros.h
> deleted file mode 100644
> index e69de29..0000000
>
> [jgarzik@pretzel linux-2.6]$ git checkout -f
>
> [jgarzik@pretzel linux-2.6]$ git checkout master && git diff
> HEADSwitched to branch "master"
>
> [jgarzik@pretzel linux-2.6]$ git checkout master && git diff HEAD
> Switched to branch "master"
>
> [jgarzik@pretzel linux-2.6]$
>
>
> So, not a git problem but a kernel Makefile problem. Sorry for the git
> noise.
distclean on purpose delete zero size files.
And the kernel tree shall not contain such files - if it does it is a bug.
So I do not see a 'problem' with the kernel makefile but instead a problem
with the kernel tree wich is about to be fixed.
Agree?
Sam
next prev parent reply other threads:[~2007-07-14 7:44 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 [this message]
2007-07-02 14:24 ` Marco Roeland
2007-07-03 0:28 ` Bryan Wu
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=20070714074558.GA8047@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=git@vger.kernel.org \
--cc=jeff@garzik.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=raa.lkml@gmail.com \
--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).