Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] python-daemonize: new package
Date: Fri, 27 Apr 2018 23:25:14 +0200	[thread overview]
Message-ID: <20180427232514.544e05ec@windsurf> (raw)
In-Reply-To: <20180411163713.13183-1-lionel@svkt.org>

Hello,

On Wed, 11 Apr 2018 18:37:12 +0200, Lionel Flandrin wrote:
> Library to enable your code run as a daemon process on Unix-like
> systems.
> 
> Signed-off-by: Lionel Flandrin <lionel@svkt.org>
> ---
>  package/Config.in                              |  1 +
>  package/python-daemonize/Config.in             |  8 ++++++++
>  package/python-daemonize/python-daemonize.hash |  3 +++
>  package/python-daemonize/python-daemonize.mk   | 14 ++++++++++++++
>  4 files changed, 26 insertions(+)
>  create mode 100644 package/python-daemonize/Config.in
>  create mode 100644 package/python-daemonize/python-daemonize.hash
>  create mode 100644 package/python-daemonize/python-daemonize.mk

I've squashed your PATCH 2/2 into PATCH 1/2, because the change to the
DEVELOPERS file should be done in the commit as the commit adding the
package. I've done no other change, it looked OK to me.

I'm adding Yegor in Cc, in case he wants to have a look a this Python
package.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

      parent reply	other threads:[~2018-04-27 21:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-11 16:37 [Buildroot] [PATCH 1/2] python-daemonize: new package Lionel Flandrin
2018-04-11 16:37 ` [Buildroot] [PATCH 2/2] DEVELOPERS: Add Lionel Flandrin to package/python-daemonize Lionel Flandrin
2018-04-27 21:25 ` 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=20180427232514.544e05ec@windsurf \
    --to=thomas.petazzoni@bootlin.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