From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Review of FOSDEM 2014 meeting action points
Date: Wed, 8 Oct 2014 18:14:24 +0200 [thread overview]
Message-ID: <20141008181424.27e753c8@free-electrons.com> (raw)
In-Reply-To: <CAGduivy-PEV9kqjD50yhKc3T8=iZa6cdg-q0Z48dQvA4SnYg1g@mail.gmail.com>
Dear Maxime Hadjinlian,
On Wed, 8 Oct 2014 13:01:56 +0200, Maxime Hadjinlian wrote:
> >> - SystemV/systemd init scripts. The idea was to do automatic
> >> installation of init scripts / service files located in
> >> package/<foo>/. Maxime Hadjinlian said he would work on this, but
> >> not much happened. On a related note, there is a need to separate
> >> the skeleton to not avoid Busybox-related init scripts in a pure
> >> systemd configuration.
> I know.. shame on me.
No problem. The point of doing a review of the action points is
definitely *not* to put the blame on anybody.
> I still have a branch with a beginning of something. I would *really*
> like to finish this during the dev-days, it would be great.
Ok. Though from my perspective, active development could better take
place outside of the dev-days. Maybe focusing the dev-days on
cleaning up the patchwork backlog is a better idea.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-10-08 16:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 8:48 [Buildroot] Review of FOSDEM 2014 meeting action points Thomas Petazzoni
2014-10-08 8:54 ` Samuel Martin
2014-10-08 11:01 ` Maxime Hadjinlian
2014-10-08 16:14 ` Thomas Petazzoni [this message]
2014-10-08 16:24 ` Gustavo Zacarias
2014-10-08 16:18 ` Thomas Petazzoni
2014-10-08 11:17 ` Jeremy Rosen
2014-10-08 16:14 ` Thomas Petazzoni
2014-10-08 11:43 ` Thomas De Schampheleire
2014-10-08 16:16 ` Thomas Petazzoni
2014-10-08 16:40 ` Matthew Weber
2014-10-08 16:43 ` Thomas Petazzoni
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=20141008181424.27e753c8@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 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.