From: Julia Lawall <julia.lawall@inria.fr>
To: Karolina Drobnik <karolinadrobnik@gmail.com>
Cc: Alison Schofield <alison.schofield@intel.com>,
Outreachy Linux Kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [Outreachy kernel] Help maintain the First Patch Tutorial
Date: Mon, 18 Oct 2021 16:18:16 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2110181617500.3174@hadrien> (raw)
In-Reply-To: <4a2104cc5bc67387300aedfb2508f991e11bed44.camel@gmail.com>
On Mon, 18 Oct 2021, Karolina Drobnik wrote:
> Hi Julia,
>
> Thanks for taking a look at my changes. I'll update the section
> accordingly after getting more feedback, hope it's fine.
>
> On Mon, 2021-10-18 at 12:12 +0200, Julia Lawall wrote:
> > > The many arguments to get_maintainer.pl cause the output to be in
> > > the form of a comma-separated list and cause only the actual
> > > maintainers of the affected files to be included. However, for IIO
> > > drivers, please also include linux-iio@vger.kernel.org.
> >
> > I wonder if this sentence is still needed, if we are dropping the
> > suggestion to use the --nol argument.
>
> I'd like to still explain what the output would be like. The "actual
> maintainers" can also refer to `--nogit-faillback` option that excludes
> committers/git information. Can change it to something like "relevant
> lists and the actual maintainers..". What do you think?
Sorry to be unclear. I was only thinking that the sentence about the IIO
drivers is no longer needed.
julia
>
> > > The second step to submitting a patch is to create and send a patch
> > > as an email. You cannot send patches as attachments to the mailing
> > > list.
> >
> > This would be better as "You cannot send a patch as an attachment..."
>
> Can correct this, thanks.
>
>
> Karolina
>
>
>
>
next prev parent reply other threads:[~2021-10-18 14:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 17:42 Help maintain the First Patch Tutorial Alison Schofield
2021-10-18 9:59 ` [Outreachy kernel] " Karolina Drobnik
2021-10-18 10:12 ` Julia Lawall
2021-10-18 14:01 ` Karolina Drobnik
2021-10-18 14:18 ` Julia Lawall [this message]
2021-10-18 17:54 ` Alison Schofield
2021-10-19 6:19 ` Greg KH
2021-10-19 15:36 ` Alison Schofield
2021-10-19 15:52 ` Greg KH
2021-10-20 13:00 ` Karolina Drobnik
2021-10-20 14:50 ` Alison Schofield
2021-10-19 9:01 ` Karolina Drobnik
2021-10-19 9:04 ` Julia Lawall
2021-10-25 11:44 ` Karolina Drobnik
2021-10-25 16:30 ` Alison Schofield
2021-10-26 12:33 ` Karolina Drobnik
2021-10-27 14:48 ` Karolina Drobnik
2021-10-27 19:20 ` Alison Schofield
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=alpine.DEB.2.22.394.2110181617500.3174@hadrien \
--to=julia.lawall@inria.fr \
--cc=alison.schofield@intel.com \
--cc=karolinadrobnik@gmail.com \
--cc=outreachy-kernel@googlegroups.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.