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] package/musl: Make scheduler functions Linux-compatible
Date: Tue, 14 May 2019 18:33:56 +0200	[thread overview]
Message-ID: <20190514183356.50c06a52@windsurf> (raw)
In-Reply-To: <071f102e7135306dfdba3203fbd35bdc07aa185f.camel@gmail.com>

Hello Stefan,

On Tue, 14 May 2019 18:32:32 +0200
stefan.nickl at gmail.com wrote:

> thanks for considering.
> This has the inner patch also generated by git.

Thanks, but could you make a proper submission of it, with a good
commit log, like you did for the first patch ?

With this new submission, the commit log would contain "thanks for
considering. This has the inner patch also generated by git", which is
not a very good commit log.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-05-14 16:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-13 20:00 [Buildroot] [PATCH] package/musl: Make scheduler functions Linux-compatible stefan.nickl at gmail.com
2019-05-13 20:13 ` Thomas Petazzoni
2019-05-14 16:32   ` stefan.nickl at gmail.com
2019-05-14 16:33     ` Thomas Petazzoni [this message]
     [not found]       ` <a03605e62a3879a0fffcbd14be04907cc3e54d3c.camel@gmail.com>
2019-05-14 16:55         ` Thomas Petazzoni
2019-05-14 17:31       ` stefan.nickl at gmail.com
2019-05-14 18:04         ` Arnout Vandecappelle
2019-05-14 18:54           ` stefan.nickl at gmail.com
2019-05-14 19:38             ` Arnout Vandecappelle
2019-05-14 20:03               ` stefan.nickl at gmail.com
2019-05-14 20:24                 ` Yann E. MORIN
2019-05-14 20:40                   ` stefan.nickl at gmail.com
2019-10-27 17:14 ` Arnout Vandecappelle

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=20190514183356.50c06a52@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