Linux CAN drivers development
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Armin Burchardt <armin@uni-bremen.de>, linux-can@vger.kernel.org
Subject: Re: slcand in init.d-scripts
Date: Mon, 08 Jun 2015 12:41:20 +0200	[thread overview]
Message-ID: <55757150.7020008@hartkopp.net> (raw)
In-Reply-To: <20150608101412.Horde.cpWZ5_FJEM-ciNcxvoY5Nkf@webmail.uni-bremen.de>

Hi Armin,

thanks for your contributions which are definitely useful!

Can you please sent 3 separate mails with the patch content in-line?

Usually 'git send-email' does this in a perfect manner.

Patches inside attachments can not be commented and discussed.

Please add some comments to patch 2 too.

Thanks & best regards,
Oliver


On 08.06.2015 12:14, Armin Burchardt wrote:
>
> Hello,
>
> to make init.d-scripts easier to write, I propose some changes to slcand:
> * write pidfile
> * set up-flag
> * do not daemonize too early
>
> Regards
> Armin

  reply	other threads:[~2015-06-08 10:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-08 10:14 slcand in init.d-scripts Armin Burchardt
2015-06-08 10:41 ` Oliver Hartkopp [this message]
2015-06-08 12:16   ` Enrico Weigelt, metux IT consult
2015-06-08 12:40     ` Armin Burchardt

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=55757150.7020008@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=armin@uni-bremen.de \
    --cc=linux-can@vger.kernel.org \
    /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