From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/3 v3] skeleton: move ifupdown script to their own package
Date: Tue, 4 Jul 2017 23:49:34 +0200 [thread overview]
Message-ID: <20170704234934.458e6239@windsurf> (raw)
In-Reply-To: <cover.1499006091.git.yann.morin.1998@free.fr>
Hello,
On Sun, 2 Jul 2017 16:35:16 +0200, Yann E. MORIN wrote:
> Yann E. MORIN (3):
> package/ifupdown-scripts: new package
> package/ifupdown-scripts: not needed for systemd-networkd
> package/ifupdown-scripts: allow use with a custom skeleton
I've applied those patches. As discussed with Arnout and you, I've
squashed PATCH 1 and PATCH 2. And in PATCH 1, I've removed the empty
IFUPDOWN_SCRIPTS_SOURCE variable.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-04 21:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-02 14:35 [Buildroot] [PATCH 0/3 v3] skeleton: move ifupdown script to their own package Yann E. MORIN
2017-07-02 14:35 ` [Buildroot] [PATCH 1/3 v3] package/ifupdown-scripts: new package Yann E. MORIN
2017-07-02 16:04 ` Arnout Vandecappelle
2017-07-02 16:05 ` Arnout Vandecappelle
2017-07-03 9:38 ` Yann E. MORIN
2017-07-02 14:35 ` [Buildroot] [PATCH 2/3 v3] package/ifupdown-scripts: not needed for systemd-networkd Yann E. MORIN
2017-07-02 16:06 ` Arnout Vandecappelle
2017-07-02 14:35 ` [Buildroot] [PATCH 3/3 v3] package/ifupdown-scripts: allow use with a custom skeleton Yann E. MORIN
2017-07-02 16:08 ` Arnout Vandecappelle
2017-07-02 16:37 ` Yann E. MORIN
2017-07-04 21:49 ` Thomas Petazzoni [this message]
2017-07-04 21:56 ` [Buildroot] [PATCH 0/3 v3] skeleton: move ifupdown script to their own package Yann E. MORIN
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=20170704234934.458e6239@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.