From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] How to generate license report?
Date: Tue, 27 Mar 2018 10:42:48 +0200 [thread overview]
Message-ID: <20180327084246.yl4eb6qc4j52yseu@falbala.home.lespocky.de> (raw)
In-Reply-To: <20180327074335.sm7nnxydkwgu6mp2@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 853 bytes --]
Hello,
On Tue, Mar 27, 2018 at 09:43:35AM +0200, Michael Olbrich wrote:
> I want to move this stuff out of rules/post/ and do something similar to
> the image rules. And then hook up these new packages these packages
> somewhere. I'm not sure 'world' is the correct place, so a new command
> 'ptxdist license-report'?
> Any opinions on this?
From user side of view, a new command would be easy to find, that's
where I looked in the first place. Having the license-report kind of
parallel to creating 'images' or 'docs' seems reasonable to me.
Greets
Alex
--
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: C28E E6B9 0263 95CF 8FAF 08FA 34AD CD00 7221 5CC6 ***
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2018-03-27 8:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 9:51 Alexander Dahl
2018-03-22 10:09 ` [ptxdist] [PATCH] ptxdist: Add switch to generate PDF license report Denis OSTERLAND
2018-03-26 7:44 ` [ptxdist] How to generate license report? Roland Hieber
2018-03-26 7:54 ` [ptxdist] [PATCH] doc: ref parameter: document special make target 'license-report' Roland Hieber
2018-03-27 7:43 ` [ptxdist] How to generate license report? Michael Olbrich
2018-03-27 8:42 ` Alexander Dahl [this message]
2018-03-27 9:26 ` Alm, Michael
2018-03-28 20:31 ` Andreas Pretzsch
2018-03-29 7:31 ` Denis OSTERLAND
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=20180327084246.yl4eb6qc4j52yseu@falbala.home.lespocky.de \
--to=post@lespocky.de \
--cc=ptxdist@pengutronix.de \
/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