All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alison Schofield <alison.schofield@intel.com>
To: Deepak R Varma <drv@mailo.com>
Cc: Outreachy Linux Kernel <outreachy@lists.linux.dev>
Subject: Re: [Outreachy] Wiki updated needed - Patchset Subject
Date: Mon, 24 Oct 2022 14:12:46 -0700	[thread overview]
Message-ID: <Y1b/zhLlbI/NmdFR@aschofie-mobl2> (raw)
In-Reply-To: <Y1N/wsr+Wd6sEaDf@debian-BULLSEYE-live-builder-AMD64>

On Sat, Oct 22, 2022 at 10:59:38AM +0530, Deepak R Varma wrote:
> On Sun, Oct 23, 2022 at 06:51:11PM -0700, Alison Schofield wrote:
> > Greg KH has mentioned this a couple of times lately -
> >
> > >> Any reason you do not have "staging: vt6655:" as the prefix for
> > >> this 0/X email subject line?
> > >>
> > >> thanks,
> > >>
> > >> greg k-h
> >
> > A quick peek in the tutorial tells me it could be made clearer.
> > It needs to explicitly say the prefix is required, and then
> > make sure any examples do it.
> 
> Hello Alison,
> There already is a section named "Patch Subject formatting" on this link [1]
> with enough description to determine the patch subject prefix. Can you please
> review and confirm where we should improve further to make it clearer??
> 
> 	[1] https://kernelnewbies.org/PatchPhilosophy
> 
> Thank you,
> ./drv


In https://kernelnewbies.org/Outreachyfirstpatch

The example cover letter in 'Submitting a Patchset' has the
subject "[RFC 0/7] Update REPORTING-BUGS", with no subsys.
It is also confusing because the cover letter is an RFC and
the patches are a mix of RFC and PATCH. Very atypical.

Let's replace this example with one that was actually submitted
and accepted by an Outreachy Intern.  No slight intended to the
existing set as it contains an interesting set of changes. However,
an example for newbies might better come from newbies.

How about a patchset off this list? 

Would you mind using this one of yours:
[PATCH v4 00/11] staging: r8188eu: trivial code cleanup patches
but trim it to 3-4 patches plus the cover.

It's not a trivial edit, because you need to replace all the
example steps with the new patchset content.

Thanks,
Alison

> 
> >
> > Thanks,
> > Alison
> >
> 
> 

  reply	other threads:[~2022-10-24 21:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24  1:51 [Outreachy] Wiki updated needed - Patchset Subject Alison Schofield
2022-10-22  5:29 ` Deepak R Varma
2022-10-24 21:12   ` Alison Schofield [this message]
2022-10-25 20:27     ` Deepak R Varma
2022-10-25 22:30     ` Deepak R Varma
2022-10-27 22:06       ` Deepak R Varma
2022-10-28  2:33         ` Alison Schofield
2022-10-28 18:59           ` Deepak R Varma
2022-10-28 20:32             ` Alison Schofield
2022-10-31 21:15               ` Deepak R Varma
2022-10-31 21:25                 ` Deepak R Varma
2022-10-31 21:33                 ` Julia Lawall
2022-11-01  1:39                   ` Alison Schofield
2022-11-01  5:01                     ` Deepak R Varma
2022-11-02  3:35                       ` 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=Y1b/zhLlbI/NmdFR@aschofie-mobl2 \
    --to=alison.schofield@intel.com \
    --cc=drv@mailo.com \
    --cc=outreachy@lists.linux.dev \
    /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.