Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Why have legal info for host packages?
Date: Fri, 7 Jun 2013 18:23:03 +0200	[thread overview]
Message-ID: <20130607182303.0ca6ba3d@skate> (raw)
In-Reply-To: <20130607154649.GA6124@free.fr>

Dear Yann E. MORIN,

On Fri, 7 Jun 2013 17:46:49 +0200, Yann E. MORIN wrote:

> > Yes, but as we discussed some time ago, the host packages should either
> > be identified as such in the legal info, or even maybe a separate
> > manifest.csv file should be generated for the host packages.
> 
> Indeed. I never said otherwise. I was just pointing out that we also
> want to generate it for host packages, and was giving an example why
> this was needed.
> 
> That this legal-info stuff be generated in a separate location (file,
> dir) is orthogonal: we want it generated.

Agreed. But the way your e-mail was written could be understood as "the
way things are currently is correct, we don't want to change it", which
is why I reacted to it.

But anyway, I know we both agree :)

Thanks,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2013-06-07 16:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-02 16:12 [Buildroot] Why have legal info for host packages? Danomi Manchego
2013-06-02 16:19 ` Yann E. MORIN
2013-06-07  9:51   ` Thomas Petazzoni
2013-06-07 15:46     ` Yann E. MORIN
2013-06-07 16:23       ` Thomas Petazzoni [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=20130607182303.0ca6ba3d@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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