From: Thomas Huth <thuth@redhat•com>
To: Alexey Kardashevskiy <aik@ozlabs•ru>
Cc: linuxppc-dev@lists•ozlabs.org,
Nikunj A Dadhania <nikunj@linux•vnet.ibm.com>,
Benjamin Herrenschmidt <benh@kernel•crashing.org>,
slof@lists•ozlabs.org, qemu-ppc@nongnu•org
Subject: Re: [PATCH slof] README: Update with patch submittion note
Date: Mon, 6 Jul 2015 10:14:30 +0200 [thread overview]
Message-ID: <20150706101430.6a701092@thh440s> (raw)
In-Reply-To: <559A35F8.3080301@ozlabs.ru>
On Mon, 6 Jul 2015 18:02:00 +1000
Alexey Kardashevskiy <aik@ozlabs•ru> wrote:
> On 07/06/2015 05:22 PM, Thomas Huth wrote:
> > On Mon, 6 Jul 2015 14:09:10 +1000
> > Alexey Kardashevskiy <aik@ozlabs•ru> wrote:
> >
> >> This adds a maillist and emails to be used when posting a patch for SLOF.
...
> >> I was asked to describe somewhere how to post new patches so this is the first
> >> attempt. Please fix my english and add/remove personal emails and any other
> >> comments are also welcome. Thanks!
> >
> > I think you should add least add a sentence that the subject should
> > contain "[SLOF PATCH...]", so that people on the list can see at a
> > first glance that the patch is about SLOF.
>
> Patches for SLOF should be made against https://github.com/aik/SLOF,
> the master branch and posted to slof@ozlabs•org.
Great, thanks for creating the list!
> It is recommended cc: to aik@ozlabs•ru, nikunj@linux•vnet.ibm.com,
> thuth@redhat•com.
Since that list is likely low-traffic only, I think I will have a look
at each mail I get on that list, so you can at least remove me from the
CC: list here.
Thomas
next prev parent reply other threads:[~2015-07-06 8:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 4:09 [PATCH slof] README: Update with patch submittion note Alexey Kardashevskiy
2015-07-06 5:03 ` Nikunj A Dadhania
2015-07-06 7:22 ` Thomas Huth
2015-07-06 8:02 ` Alexey Kardashevskiy
2015-07-06 8:14 ` Thomas Huth [this message]
2015-07-06 8:29 ` Nikunj A Dadhania
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=20150706101430.6a701092@thh440s \
--to=thuth@redhat$(echo .)com \
--cc=aik@ozlabs$(echo .)ru \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=nikunj@linux$(echo .)vnet.ibm.com \
--cc=qemu-ppc@nongnu$(echo .)org \
--cc=slof@lists$(echo .)ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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