From: Lourdes Pedrajas <lu@pplo.net>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: Stefano Brivio <sbrivio@redhat.com>,
outreachy-kernel@googlegroups.com, gregkh@linuxfoundation.org
Subject: Re: [Outreachy kernel] [PATCH] staging: greybus: remove commented out function
Date: Mon, 9 Mar 2020 17:38:04 +0100 [thread overview]
Message-ID: <20200309163804.GB3949@supernova> (raw)
In-Reply-To: <alpine.DEB.2.21.2003091729360.4721@hadrien>
On Mon, Mar 09, 2020 at 05:30:25PM +0100, Julia Lawall wrote:
>
>
> On Mon, 9 Mar 2020, Lourdes Pedrajas wrote:
>
> > On Mon, Mar 09, 2020 at 12:53:27PM +0100, Stefano Brivio wrote:
> > > On Sun, 8 Mar 2020 23:22:18 +0100
> > > Lourdes Pedrajas <lu@pplo.net> wrote:
> > >
> > > However, you should at least Cc: the maintainers returned by
> > > get_maintainer.pl.
> > >
> > Yes, I was about to ask because I read somewhere in kernelnewbies wiki that
> > Outreachy paths hould no be CCd to everyone in the get_maintainer.pl list,
> > but I was wondering if this was really correct. So thank you for the hint!
>
> Please search for get_maintainer in the tutorial and follow the
> instructions there. It gives some options that will get your patch to the
> main people who are responsible for the file.
>
> julia
Yes, if is not too much spam I will resend the patches including
them, thank you!
next prev parent reply other threads:[~2020-03-09 16:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-08 22:22 [PATCH] staging: greybus: remove commented out function Lourdes Pedrajas
2020-03-09 11:53 ` [Outreachy kernel] " Stefano Brivio
2020-03-09 16:26 ` Lourdes Pedrajas
2020-03-09 16:30 ` Julia Lawall
2020-03-09 16:38 ` Lourdes Pedrajas [this message]
2020-03-10 9:11 ` Greg KH
2020-03-09 17:19 ` Vaishali Thakkar
2020-03-09 19:45 ` Lourdes Pedrajas
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=20200309163804.GB3949@supernova \
--to=lu@pplo.net \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@inria.fr \
--cc=outreachy-kernel@googlegroups.com \
--cc=sbrivio@redhat.com \
/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.