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 v4 1/4] Add yp-tools and ypbind-mt to packages menu
Date: Sun, 24 Jan 2016 16:38:27 +0100	[thread overview]
Message-ID: <20160124163827.7984d2e1@free-electrons.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1601241724060.4122@tanhuma.tkos.co.il>

Dear Jonathan Ben Avraham,

On Sun, 24 Jan 2016 17:33:24 +0200 (IST), Jonathan Ben Avraham wrote:

> That is, one patch should look something like
> 
>  	source "package/xinetd/Config.in"
>  	source "package/xl2tp/Config.in"
>  	source "package/xtables-addons/Config.in"
>   +	source "package/yp-tools/Config.in"
>  	source "package/znc/Config.in"

This change should be part of the patch adding package/yp-tools/.

> and the other should look like
> 
>  	source "package/xinetd/Config.in"
>  	source "package/xl2tp/Config.in"
>  	source "package/xtables-addons/Config.in"
>   +	source "package/ypbind-mt/Config.in"
>  	source "package/znc/Config.in"

This change should be part of the patch adding package/ypbind-mt/

> And then we rely on the order of the application of the patches to 
> determine the order of the items in the final Config.in?

Yes. A series is a list of patches that are ordered. They will be
applied in the order they are listed in your series. Many series have
patches that have dependencies between each other, that's the whole
purpose of sending them as a series rather than independently.

Thanks!

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

  reply	other threads:[~2016-01-24 15:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-24 14:54 [Buildroot] [PATCH v4 0/4] yp-tools, ypbind-mt: new packages Jonathan Ben-Avraham
2016-01-24 14:55 ` [Buildroot] [PATCH v4 1/4] Add yp-tools and ypbind-mt to packages menu Jonathan Ben-Avraham
2016-01-24 15:09   ` Thomas Petazzoni
2016-01-24 15:33     ` Jonathan Ben Avraham
2016-01-24 15:38       ` Thomas Petazzoni [this message]
2016-01-24 15:47         ` Jonathan Ben Avraham
2016-01-24 14:55 ` [Buildroot] [PATCH v4 2/4] linux-pam: Enable NIS support if yp-tools selected Jonathan Ben-Avraham
2016-01-24 15:09   ` Thomas Petazzoni
2016-01-24 15:36     ` Jonathan Ben Avraham
2016-01-24 15:51       ` Thomas Petazzoni
2016-01-24 14:55 ` [Buildroot] [PATCH v4 3/4] yp-tools: new package Jonathan Ben-Avraham
2016-01-24 14:55 ` [Buildroot] [PATCH v4 4/4] ypbind-mt: " Jonathan Ben-Avraham

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=20160124163827.7984d2e1@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