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] help entries for Init system config menu
Date: Sun, 18 Oct 2015 23:46:32 +0200	[thread overview]
Message-ID: <20151018234632.2cd5d3a6@free-electrons.com> (raw)
In-Reply-To: <20150324202302.GA4645@vostro>

Dear Alex Suykov,

On Tue, 24 Mar 2015 22:23:02 +0200, Alex Suykov wrote:
> Primary focus is on (auto-)respawning and runtime control.
> 
> Systemd entry describes current state, with several daemons
> configured as forking.
> 
> Signed-off-by: Alex Suykov <alex.suykov@gmail.com>

The only feedback received formally on the list on this patch was from
Yann E. Morin, and his feedback was not very positive. We
quickly discussed your patch as the latest Buildroot meeting, and some
people found part of it interesting (such as the parts detailing how in
Buildroot each init system is implemented: rcS + Sxx scripts, etc.),
but that it is not acceptable in this form.

However, this you have never reacted to Yann's feedback, I am not sure
if you are still interested in getting this patch merged. I've marked
it as "Rejected" for now as it isn't acceptable in its current form.

If you're interested in pushing this further, can you reply to Yann's
feedback ?

Thanks,

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

      parent reply	other threads:[~2015-10-18 21:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24 20:23 [Buildroot] [PATCH] help entries for Init system config menu Alex Suykov
2015-04-08 21:12 ` Yann E. MORIN
2015-10-18 21:46 ` 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=20151018234632.2cd5d3a6@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