From: "akuster" <akuster808@gmail.com>
To: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] README: A couple of updates due to recent changes
Date: Mon, 10 Feb 2020 09:00:54 -0800 [thread overview]
Message-ID: <f2b93c68-e11f-0007-f2e9-1cb5403461d0@gmail.com> (raw)
In-Reply-To: <20200210033743.24295-1-tanuk@iki.fi>
[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]
On 2/9/20 7:37 PM, Tanu Kaskinen wrote:
> Since there's now a separate mailing list for docs, I think the
> yocto-docs tag doesn't need to be added to patches any more.
>
> ---
>
> README | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/README b/README
> index 62c2a3ffb..6a7f3abe6 100644
> --- a/README
> +++ b/README
> @@ -11,15 +11,13 @@ Where to Send Patches
> =====================
>
> When sending single patches, please using something like:
> -'git send-email -1 --to docs@lists.yoctoproject.org --subject-prefix=yocto-docs][PATCH'
> +'git send-email -1 --to docs@lists.yoctoproject.org
We still need a subject
>
> -These values can be set as defaults for this repository:
> +The To header can be set as default for this repository:
>
> $ git config sendemail.to docs@lists.yoctoproject.org
> -$ git config format.subjectPrefix yocto-docs][PATCH
We still need a subject
>
> Now you can just do 'git send-email origin/master' to send all local patches.
>
> Git repository: http://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/
> Mailing list: docs@lists.yoctoproject.org
> -Please cc: Scott Rifenbark <srifenbark@gmail.com> on changes.
>
>
[-- Attachment #2: Type: text/html, Size: 2472 bytes --]
next prev parent reply other threads:[~2020-02-10 17:00 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 ` akuster [this message]
2020-02-11 1:01 ` [docs] " 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
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=f2b93c68-e11f-0007-f2e9-1cb5403461d0@gmail.com \
--to=akuster808@gmail.com \
--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.