From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] Makefile: add target to clean targetfs
Date: Sun, 4 Oct 2015 17:56:08 +0100 [thread overview]
Message-ID: <56115A28.9020001@mind.be> (raw)
In-Reply-To: <1430095555-8484-1-git-send-email-emeric.vigier@savoirfairelinux.com>
On 27-04-15 01:45, Emeric Vigier wrote:
> If you had some files added to the targetfs (fs-overlay, new packages,
> ...) and you no longer need them, buildroot does not offer a simple way
> to remove these items from the output/target directory. The rule added
> by this commit allows you to clean the targetfs. Issuing 'make'
> afterward will generate a new and clean targetfs.
>
> A section in the documentation is also added. It describes few examples
> when developers could need it. 'make help' is also updated accordingly.
> And full-rebuild section of the documentation is updated with content
> and links.
>
> Change-Id: I42b640e845bb4195fb7b160281b16ee40883f01f
> Signed-off-by: Emeric Vigier <emeric.vigier@savoirfairelinux.com>
Hi Emeric,
Since there were some comments on this patch and there also seem to be cases
where it doesn't really work well, I've marked it as Changes Requested in our
patch tracking system. So unless you resubmit a new version that fixes the
comments, we will forget about your contribution.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
prev parent reply other threads:[~2015-10-04 16:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 0:25 [Buildroot] [PATCH 1/1] Makefile: add target to clean targetfs Emeric Vigier
2015-03-10 4:45 ` Baruch Siach
2015-03-10 14:56 ` Emeric Vigier
2015-03-10 15:17 ` Baruch Siach
2015-03-10 19:28 ` [Buildroot] [PATCH v2 " Emeric Vigier
2015-03-10 23:41 ` Ryan Barnett
2015-03-11 5:06 ` Baruch Siach
2015-03-11 8:22 ` Angelo Compagnucci
2015-03-11 8:58 ` Baruch Siach
2015-03-12 8:32 ` Angelo Compagnucci
2015-03-12 14:56 ` Emeric Vigier
2015-03-12 14:44 ` Emeric Vigier
2015-03-12 14:46 ` Ryan Barnett
2015-03-12 8:36 ` Angelo Compagnucci
2015-03-12 15:59 ` Jérôme Oufella
2015-04-27 0:45 ` [Buildroot] [PATCH v3 " Emeric Vigier
2015-04-27 4:11 ` Baruch Siach
2015-04-28 14:36 ` Emeric Vigier
2015-04-27 8:28 ` Andreas Naumann
2015-04-28 15:06 ` Emeric Vigier
2015-07-14 21:56 ` Emeric Vigier
2015-07-16 15:15 ` Emeric Vigier
2015-07-23 20:51 ` Andreas Naumann
2015-10-04 16:56 ` Arnout Vandecappelle [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=56115A28.9020001@mind.be \
--to=arnout@mind.be \
--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