All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emily Peri <eperi1024@gmail.com>
To: Alison Schofield <alison.schofield@intel.com>
Cc: Outreachy Linux Kernel <outreachy@lists.linux.dev>
Subject: Re: [Outreachy Info] Track patches in staging tree
Date: Fri, 21 Oct 2022 09:39:49 -0700	[thread overview]
Message-ID: <Y1LLVSNEwewWntrF@marshmallow> (raw)
In-Reply-To: <Y1GE6ImSoBuYCTjT@aschofie-mobl2>

On Thu, Oct 20, 2022 at 10:27:04AM -0700, Alison Schofield wrote:
> 
> In case you are wondering the status of your patches -
> 
> When GregKH accepts your patch you get an acknowledgment email directly.
> If he specifically rejects it, you also get feedback from him on what
> to improve. He won't accept a patch where another reviewer has already
> requested an update. So, once you get any feedback, revise and send the
> new version.

Thanks for the clarification! One lingering question I have-- I sent in
a patchset and got feedback on one of the patches in the set, so I'm
planning to revise it today. I noticed though that Greg accepted the
other patches in the patchset and I got a notification that those will
be merged. Is that how it usually works with patchsets? Can the other
patches in the set be merged is one of them needs revision?

> You can follow the staging-testing tree [1] and see if Greg has 
> merged patches since your submittal. Those *are* accepted patches
> and should be recorded as contributions in your Outreachy dashboard.
> 
> Occasionally a patch gets missed in a flurry of patches. That might
> make you think about RESENDing. See the tutorial directions about
> resending.
> 
> For example, at this moment I can see that Tanjuate, Deepak, and
> Emily (sorry if I'm not recognizing another name yet) had patches
> accepted in the last couple of hours.
> 
> Hope that's useful,
> Alison
> 
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/log/?h=staging-testing
> 
> 

  parent reply	other threads:[~2022-10-21 16:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20 17:27 [Outreachy Info] Track patches in staging tree Alison Schofield
2022-10-20 17:35 ` Deepak R Varma
2022-10-20 18:09 ` Alison Schofield
2022-10-21 16:39 ` Emily Peri [this message]
2022-10-21 16:49   ` Julia Lawall

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=Y1LLVSNEwewWntrF@marshmallow \
    --to=eperi1024@gmail.com \
    --cc=alison.schofield@intel.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.