From: "Jike Song" <albcamus@gmail.com>
To: sam@ravnborg.org
Cc: linux-kbuild@vger.kernel.org
Subject: Do we really need file `all'?
Date: Tue, 30 Dec 2008 14:17:26 +0800 [thread overview]
Message-ID: <df9815e70812292217p65b6285eo7a7909c0f6899e6e@mail.gmail.com> (raw)
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,
Jike
next reply other threads:[~2008-12-30 6:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 6:17 Jike Song [this message]
2008-12-30 7:36 ` Do we really need file `all'? Jike Song
2008-12-30 9:24 ` Sam Ravnborg
2008-12-30 9:28 ` Jike Song
2008-12-30 9:22 ` 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=df9815e70812292217p65b6285eo7a7909c0f6899e6e@mail.gmail.com \
--to=albcamus@gmail.com \
--cc=linux-kbuild@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