From: Sam Ravnborg <sam@ravnborg.org>
To: Jike Song <albcamus@gmail.com>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: Do we really need file `all'?
Date: Tue, 30 Dec 2008 10:22:49 +0100 [thread overview]
Message-ID: <20081230092249.GA27321@uranus.ravnborg.org> (raw)
In-Reply-To: <df9815e70812292217p65b6285eo7a7909c0f6899e6e@mail.gmail.com>
On Tue, Dec 30, 2008 at 02:17:26PM +0800, Jike Song wrote:
> Hi Sam,
>
> In commit a680eedc6c621c75695c68198533fc3c98f4053b you introduced the
> following code:
>
> exuberant()
> {
> all_sources > all
> all_sources | xargs ....{snip}...
>
> This will generate a regular file named `all' in the repository, which
> is not included in .gitignore.
> Do we really need this file? I think the second run of all_source is
> enough. Or otherwise should
> we add it into .gitignore?
>
> I'm not subscribing linux-kbuild list so please CC me in replies, thanks.
Thanks for the report. I have queued following fix:
Sam
From da20e8358e3408a208a2a7056eaff550c8644c9d Mon Sep 17 00:00:00 2001
From: Sam Ravnborg <sam@ravnborg.org>
Date: Tue, 30 Dec 2008 10:20:08 +0100
Subject: [PATCH] kbuild: drop debugging leftover in tags.sh
Noticed by Jike.
Reported-by: "Jike Song" <albcamus@gmail.com>
Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
---
scripts/tags.sh | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/scripts/tags.sh b/scripts/tags.sh
index 4e75472..9e3451d 100755
--- a/scripts/tags.sh
+++ b/scripts/tags.sh
@@ -84,7 +84,6 @@ docscope()
exuberant()
{
- all_sources > all
all_sources | xargs $1 -a \
-I __initdata,__exitdata,__acquires,__releases \
-I __read_mostly,____cacheline_aligned \
--
1.6.0.2.GIT
prev parent reply other threads:[~2008-12-30 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 6:17 Do we really need file `all'? Jike Song
2008-12-30 7:36 ` Jike Song
2008-12-30 9:24 ` Sam Ravnborg
2008-12-30 9:28 ` Jike Song
2008-12-30 9:22 ` Sam Ravnborg [this message]
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=20081230092249.GA27321@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=albcamus@gmail.com \
--cc=linux-kbuild@vger.kernel.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