From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [RFC] Script to find used sources in the kernel
Date: Tue, 03 Dec 2019 11:40:04 +0000 [thread overview]
Message-ID: <45be3f5986a1c19dfb65fc5c4d2d104ef757a0ae.camel@codethink.co.uk> (raw)
In-Reply-To: <20191126193119.GA4125793@pollux.denx.de>
On Tue, 2019-11-26 at 20:31 +0100, Pavel Machek wrote:
> Hi!
>
> (Ressurecting old discussion).
>
> On Wed 2019-07-10 18:45:38, Ben Hutchings wrote:
> > On Sat, 2019-06-22 at 22:07 +0200, Pavel Machek wrote:
> > > 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've implemented that option.
>
> Are the lists stored somewhere?
Yes they are the *.sources files.
> I see the scripts in "cip-kernel-config"
> but I guess it needs non-trivial setup. I'd eventually like filtered version
> in lts-commit-list repository.
[...]
They require a kernel repository with the CIP branches, and suitable
compilers installed.
Ben.
Pavel
--
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom
prev parent reply other threads:[~2019-12-03 11:40 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
2019-07-10 17:45 ` Ben Hutchings
2019-11-26 19:31 ` Pavel Machek
2019-12-03 11:40 ` Ben Hutchings [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=45be3f5986a1c19dfb65fc5c4d2d104ef757a0ae.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--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