From: "Ulrich Ölmann" <u.oelmann@pengutronix.de>
To: PTXdist Development Mailing List <ptxdist@pengutronix.de>
Cc: "Ulrich Ölmann" <u.oelmann@pengutronix.de>
Subject: Re: [ptxdist] [PATCH 1/2] doc: dev_manual: add explanation of *_SOURCE variable
Date: Thu, 22 Aug 2019 17:31:11 +0200 [thread overview]
Message-ID: <6rv9upgqtc.fsf@pengutronix.de> (raw)
In-Reply-To: <20190822133746.12021-1-u.oelmann@pengutronix.de>
Hi there,
sending the same series of patches two times happened by accident -
please just disregard one of them.
Ulrich
On Thu, Aug 22 2019 at 15:37 +0200, Ulrich Ölmann <u.oelmann@pengutronix.de> wrote:
> Signed-off-by: Ulrich Ölmann <u.oelmann@pengutronix.de>
> ---
> doc/dev_manual.rst | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/doc/dev_manual.rst b/doc/dev_manual.rst
> index cd1d2e9fc098..e83584634c06 100644
> --- a/doc/dev_manual.rst
> +++ b/doc/dev_manual.rst
> @@ -368,6 +368,8 @@ PTXdist specific. What does it mean:
> alternative download locations are known, they can be listed in this
> variable, delimiter character is the space.
>
> +- ``*_SOURCE`` tells PTXdist where to store the downloaded package.
> +
> - ``*_DIR`` points to the directory this package will be build later on
> by PTXdist
--
Pengutronix e.K. | Ulrich Ölmann |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-08-22 15:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 13:37 Ulrich Ölmann
2019-08-22 13:37 ` [ptxdist] [PATCH 2/2] doc: dev_manual: fix typos Ulrich Ölmann
2019-08-22 15:31 ` Ulrich Ölmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-22 13:37 [ptxdist] [PATCH 1/2] doc: dev_manual: add explanation of *_SOURCE variable Ulrich Ölmann
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=6rv9upgqtc.fsf@pengutronix.de \
--to=u.oelmann@pengutronix.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