mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Roland Hieber <r.hieber@pengutronix.de>
To: Alexander Dahl <ada@thorsis.com>, ptxdist@pengutronix.de
Subject: Re: [ptxdist] How to generate license report?
Date: Mon, 26 Mar 2018 09:44:17 +0200	[thread overview]
Message-ID: <4bd8ee22-8d1d-0986-9cc2-d6bc3b2f19af@pengutronix.de> (raw)
In-Reply-To: <2481480.E6RcUUs0gu@ada>

On 22.03.2018 10:51, Alexander Dahl wrote:
> Hello,
> 
> from the Git repository and some hints in the ptxdist source code I assume
> ptxdist can generate some kind of license report, based on the FOO_LICENSE
> variables in each packages make rule. However I could not find any hint on how
> to generate this report in:
> 
> * documentation (ptxdist docs-html or on ptxdist.org)
> * `ptxdist --help`
> * `ptxdist`
> * sourcecode of ptxdist
> 
> Is it possible to generate such a report? How?

This should probably be documented. You can get it via

    $ ptxdist make license-report

  - Roland

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  parent reply	other threads:[~2018-03-26  7:44 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 ` Roland Hieber [this message]
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
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=4bd8ee22-8d1d-0986-9cc2-d6bc3b2f19af@pengutronix.de \
    --to=r.hieber@pengutronix.de \
    --cc=ada@thorsis.com \
    --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