From: Roland Hieber <rhi@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Rouven Czerwinski <r.czerwinski@pengutronix.de>
Subject: Re: [ptxdist] [PATCH] doc: document local_src clean behaviour
Date: Fri, 18 Jan 2019 10:15:44 +0100 [thread overview]
Message-ID: <20190118091544.r3hfjnelwvcj2x6q@pengutronix.de> (raw)
In-Reply-To: <20190118073642.22877-1-r.czerwinski@pengutronix.de>
On Fri, Jan 18, 2019 at 08:36:42AM +0100, Rouven Czerwinski wrote:
> For local_src directories, ptxdist only calls the clean command on a full clean,
> not for a clean with the individual package. Document this in a note for the
> workflow.
>
> Signed-off-by: Rouven Czerwinski <r.czerwinski@pengutronix.de>
> ---
> doc/daily_work.inc | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/doc/daily_work.inc b/doc/daily_work.inc
> index 47bc987e4..2636336d0 100644
> --- a/doc/daily_work.inc
> +++ b/doc/daily_work.inc
> @@ -118,6 +118,11 @@ To rebuild the kernel:
> jbe@octopus:~/myprj$ ptxdist drop kernel compile
> jbe@octopus:~/myprj$ ptxdist targetinstall kernel
>
> +.. note:: To clean the kernel, change into the local_src directory and call
> + ``make clean`` or the clean command for the build system used by the
> + package. A ``ptxdist clean kernel`` call will only delete the
> + symlinks, but not clean the kernel compiled files.
> +
I would add a "symlinks in the build directory", to distinguish them
from the symlinks in the local_src/ directory.
- Roland
--
Roland Hieber | r.hieber@pengutronix.de |
Pengutronix e.K. | https://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim | Phone: +49-5121-206917-5086 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2019-01-18 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 7:36 Rouven Czerwinski
2019-01-18 8:17 ` Michael Olbrich
2019-01-18 9:15 ` Roland Hieber [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=20190118091544.r3hfjnelwvcj2x6q@pengutronix.de \
--to=rhi@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=r.czerwinski@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