From: pavel@ucw.cz (Pavel Machek)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [RFC] Script to find used sources in the kernel
Date: Sat, 22 Jun 2019 22:07:14 +0200 [thread overview]
Message-ID: <20190622200714.GA19211@amd> (raw)
In-Reply-To: <1561048077.21054.46.camel@codethink.co.uk>
Hi!
> There are a couple of open questions, on which I would like to hear
> other's opinions:
>
> * Should the source lists be added to the repository or not? If they
> are added, then they should not be changed by the standard "all" and
> "clean" targets.
> I tend to think that they should be added, because they take a long
> time to generate and require cross-compilers etc. to be installed.
I believe they should go to the repository, because we may want to
manually adjust the lists.
I don't believe "example" configurations we have necessarily have
enabled all the options "final products" may need. If some common
option (vfat?) is not enabled in our configurations, because it is not
hardware specific and not needed for testing, we may still want to
review it, because it is common enough that someone will need it...
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190622/b2c00791/attachment.sig>
next prev parent reply other threads:[~2019-06-22 20:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 16:27 [cip-dev] [RFC] Script to find used sources in the kernel Ben Hutchings
2019-06-22 20:07 ` Pavel Machek [this message]
2019-07-10 17:45 ` Ben Hutchings
2019-11-26 19:31 ` Pavel Machek
2019-12-03 11:40 ` Ben Hutchings
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=20190622200714.GA19211@amd \
--to=pavel@ucw.cz \
--cc=cip-dev@lists.cip-project.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