From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] release: remove manual build files from release tarballs
Date: Sat, 18 Jul 2015 11:11:11 +0200 [thread overview]
Message-ID: <20150718111111.57138b33@free-electrons.com> (raw)
In-Reply-To: <1437128435-17331-1-git-send-email-patrickdepinguin@gmail.com>
Dear Thomas De Schampheleire,
On Fri, 17 Jul 2015 12:20:35 +0200, Thomas De Schampheleire wrote:
> From: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
>
> The Buildroot release tarballs inadvertently contain a build/docs directory,
> containing the manual sources, the generated lists, and manual.text and
> manual.pdf (but excluding manual.html).
>
> This directory is populated as $(BUILD_DIR) (==$(O)/build), while O is
> set explicitly from the release target to a subdirectory
> buildroot-xxxx.yy-git/ which was populated with 'git archive'.
>
> Since the generated manuals are available in docs/manual, which is
> also referred to from the README, the build directory is not needed and
> should be removed from the release tarball.
>
> Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
> ---
> Makefile | 1 +
> 1 file changed, 1 insertion(+)
Applied, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-07-18 9:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 10:20 [Buildroot] [PATCH 1/1] release: remove manual build files from release tarballs Thomas De Schampheleire
2015-07-17 16:53 ` Yann E. MORIN
2015-07-18 9:11 ` Thomas Petazzoni [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=20150718111111.57138b33@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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