From: Thomas De Schampheleire <patrickdepinguin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0 of 4 v2] Add POST_RSYNC hook
Date: Thu, 07 Nov 2013 11:41:20 +0100 [thread overview]
Message-ID: <patchbomb.1383820880@argentina> (raw)
This patch series adopts the POST_RSYNC hook patch by Tzu-Jung Lee and
changes the default rsync exclusion list, as discussed on the Buildroot
developer days.
The other rsync-related patch submitted by Tzu-Jung Lee (custom rsync
command) should not be needed anymore as its use case is covered by
the second patch in this series.
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
---
Makefile | 14 ++++++++------
docs/manual/adding-packages-autotools.txt | 3 +--
docs/manual/adding-packages-cmake.txt | 3 +--
docs/manual/adding-packages-generic.txt | 39 +--------------------------------------
docs/manual/adding-packages-hooks.txt | 61 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
docs/manual/adding-packages.txt | 2 ++
package/pkg-generic.mk | 4 +++-
7 files changed, 77 insertions(+), 49 deletions(-)
next reply other threads:[~2013-11-07 10:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 10:41 Thomas De Schampheleire [this message]
2013-11-07 10:41 ` [Buildroot] [PATCH 1 of 4 v2] infra: Add POST_RSYNC_HOOKS support Thomas De Schampheleire
2013-11-07 10:41 ` [Buildroot] [PATCH 2 of 4 v2] infra: centralize rsync exclude list for VCS files Thomas De Schampheleire
2013-11-07 10:41 ` [Buildroot] [PATCH 3 of 4 v2] manual: split info on hooks to a separate section/file Thomas De Schampheleire
2013-11-07 10:41 ` [Buildroot] [PATCH 4 of 4 v2] manual: add some info on the POST_RSYNC hook Thomas De Schampheleire
2013-11-07 10:54 ` Samuel Martin
2013-11-10 23:12 ` [Buildroot] [PATCH 0 of 4 v2] Add " Peter Korsgaard
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=patchbomb.1383820880@argentina \
--to=patrickdepinguin@gmail.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