From: "Tanu Kaskinen" <tanuk@iki.fi>
To: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] README: A couple of updates due to recent changes
Date: Tue, 11 Feb 2020 09:14:41 +0200 [thread overview]
Message-ID: <21fb56c27c2d205338a89b29246a2fe9edf82f7f.camel@iki.fi> (raw)
In-Reply-To: <3e3671e6-02fb-7560-d886-a515122757ac@gmail.com>
On Mon, 2020-02-10 at 18:07 -0800, akuster wrote:
>
> On 2/10/20 5:57 PM, Peter Kjellerstedt wrote:
> > Are you thinking of the layers in meta-openembedded? There it makes
> > sense since many layers share one mailing list. However, here we are
> > talking about the docs repository with its own mailing list. There
> > should be no other patches sent to it than those that are intended for
> > the docs repository, so there should be no need to add an extra
> > [yocto-docs] prefix.
> >
> I agree. no need to include [yocto-docs] in the subject line.
>
> I mean "git sent-email -1 -M --subject-prefix=PATCH --to
> docs@lists.yoctoproject.org"
>
> don't we want a subject? the subject part was removed from the README.
If the --subject-prefix option is not set, then git send-email will by
default generate a subject containing a "[PATCH]" prefix plus the
commit title. This patch was submitted without the --subject-prefix
option, and as you can see, the subject is fine.
I forgot to add Signed-off-by to the patch, I'll resend it.
--
Tanu
https://www.patreon.com/tanuk
https://liberapay.com/tanuk
prev parent reply other threads:[~2020-02-11 7:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 3:37 [PATCH] README: A couple of updates due to recent changes Tanu Kaskinen
2020-02-10 17:00 ` [docs] " akuster
2020-02-11 1:01 ` Peter Kjellerstedt
2020-02-11 1:33 ` akuster
2020-02-11 1:57 ` Peter Kjellerstedt
2020-02-11 2:07 ` akuster
2020-02-11 7:14 ` Tanu Kaskinen [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=21fb56c27c2d205338a89b29246a2fe9edf82f7f.camel@iki.fi \
--to=tanuk@iki.fi \
--cc=docs@lists.yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.