From: Junio C Hamano <junkio@cox.net>
To: Erik Mouw <erik@harddisk-recovery.com>
Cc: Frederik Deweerdt <deweerdt@free.fr>,
linux-kernel@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: Make kernel -dirty naming optional
Date: Mon, 25 Sep 2006 14:44:36 -0700 [thread overview]
Message-ID: <7vy7s7y62j.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060924101155.GB9271@harddisk-recovery.nl> (Erik Mouw's message of "Sun, 24 Sep 2006 12:11:55 +0200")
Erik Mouw <erik@harddisk-recovery.com> writes:
> make mrproper
> cp ../config-2.6 .config
> yes no | make oldconfig
> fakeroot make targz-pkg
fakeroot makes the working tree files appear to be owned by
root.root but does not know git uses the file ownership
information recorded in the index and uses it to detect if the
working tree is dirty. Because the index says they are owned by
you (the one who pulled from the kernel.org and owns the files
in the real world not fakeroot world), you get -dirty suffix.
Perhaps "fakeroot -u" would help.
next prev parent reply other threads:[~2006-09-25 21:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 12:02 Frederik Deweerdt
2006-09-22 10:49 ` Erik Mouw
2006-09-24 9:07 ` Sam Ravnborg
2006-09-24 10:11 ` Erik Mouw
2006-09-25 21:44 ` Junio C Hamano [this message]
2006-10-02 10:51 ` Erik Mouw
2006-09-24 9:00 ` Sam Ravnborg
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=7vy7s7y62j.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=deweerdt@free.fr \
--cc=erik@harddisk-recovery.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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
all inboxes | Powered by JetHome®