Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Allow adding per-package overrlice rsync exclusions
Date: Wed, 8 Nov 2017 18:06:29 +0100	[thread overview]
Message-ID: <20171108180629.6f7d418b@windsurf> (raw)
In-Reply-To: <20171108144635.GB28359@momiji>

Hello,

On Wed, 8 Nov 2017 14:46:35 +0200, Adrian Perez de Castro wrote:

> > Also my thinking: per-package out of tree build is going to make this
> > new feature a lot less relevant. That being said, per-package out of
> > tree build is not there yet, and this new feature is just a very simple
> > change, so I believe it's OK to merge it.  
> 
> How about packages which do not support out-of-tree builds? Wouldn't it still
> be useful to be to define additional rsync flags for them? 

Indeed, packages that don't support out of tree build will continue
using rsync, and therefore it makes sense to have this exclusion thing.

> > I think we really want the documentation update as part of the patch
> > series :)  
> 
> Good point, I'll add add the edit for the manual as well and submit a new
> version of the patch.

Thanks :)

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

      reply	other threads:[~2017-11-08 17:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-07  1:57 [Buildroot] [PATCH 1/1] Allow adding per-package overrlice rsync exclusions Adrian Perez de Castro
2017-11-07 20:57 ` Arnout Vandecappelle
2017-11-07 21:05   ` Thomas Petazzoni
2017-11-08 12:46     ` Adrian Perez de Castro
2017-11-08 17:06       ` 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=20171108180629.6f7d418b@windsurf \
    --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