From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] release: don't include temp files
Date: Sun, 10 May 2020 21:35:14 +0200 [thread overview]
Message-ID: <87r1vrshvx.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20200508083220.18927-1-yann.morin.1998@free.fr> (Yann E. MORIN's message of "Fri, 8 May 2020 10:32:20 +0200")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> When we prepare the release, we generate the manual in various formats,
> so that it can be consulted locally without needing the miriads of tools
> needed to generate it.
> However, this creates the temporary .br2-external.* files in the output
> directory, and those end up in the release tarball.
> This is not a problem in practice, but is not clean.
> Run 'distclean' in the output directory, to get rid of everything but
> the generated documentation.
> Reported-by: Danomi Manchego <danomimanchego123@gmail.com>
> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
> Cc: Peter Korsgaard <peter@korsgaard.com>
Committed to 2020.02.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2020-05-10 19:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 8:32 [Buildroot] [PATCH] release: don't include temp files Yann E. MORIN
2020-05-08 9:34 ` Peter Korsgaard
2020-05-08 13:59 ` Danomi Manchego
2020-05-08 19:59 ` Yann E. MORIN
2020-05-08 20:04 ` Danomi Manchego
2020-05-10 19:35 ` Peter Korsgaard [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=87r1vrshvx.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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