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:55:48 +0200 [thread overview]
Message-ID: <20190514185548.13b23569@windsurf> (raw)
In-Reply-To: <a03605e62a3879a0fffcbd14be04907cc3e54d3c.camel@gmail.com>
Hello,
Please keep the mailing list Cc'ed. Thanks!
On Tue, 14 May 2019 18:51:05 +0200
stefan.nickl at gmail.com wrote:
> Should I move the text all out from the patch to the commit log, or can
> I just duplicate the text inside and outside the patch?
> Or should one be more detailed and the other shorter?
The text can be similar, but it has a different target.
The commit log is meant to be useful to Buildroot, so it should explain
why in Buildroot we would want this change.
The description of the musl patch itself should theoretically be
unrelated to Buildroot: it should ideally be an upstreamable patch, and
musl doesn't care about Buildroot specifically.
So the patch description should really describe the change in terms of
the upstream project, while the commit log should describe the change
in the context of Buildroot.
Does this helps?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-05-14 16:55 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
[not found] ` <a03605e62a3879a0fffcbd14be04907cc3e54d3c.camel@gmail.com>
2019-05-14 16:55 ` Thomas Petazzoni [this message]
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=20190514185548.13b23569@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