[Outreachy Info] Track patches in staging tree

[Outreachy Info] Track patches in staging tree

[Alison Schofield]

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.

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

Re: [Outreachy Info] Track patches in staging tree

[Deepak R Varma]

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.
>
> 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

Thank you very much Alison for the update and direction. This is helpful.

./drv

>
>

Re: [Outreachy Info] Track patches in staging tree

[Alison Schofield]

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.
> 
> 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.
> 

Sometimes, GregKH is so fast ;) that he has merged your patch, and
then a reviewer comments on it - either a reviewer on this list, or
from the get_maintainers recipients. 

In that case you may just send another patch, to do what your
reviewer suggested, or if it's a log message issue, you might
say, 'Thanks, I see it, I'll do better next time, but GregKH
has already merged this patch'. And, you can always just ask
the reviewer how to handle it.

I bring this up because it happens with me on this list. I'll
comment on a commit message or log, and it is too late. That's
OK - just take my advice for next time!

> 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
> 
> 

Re: [Outreachy Info] Track patches in staging tree

[Emily Peri]

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
> 
> 

Re: [Outreachy Info] Track patches in staging tree

[Julia Lawall]

On Fri, 21 Oct 2022, Emily Peri wrote:

> 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?

Maybe he merged some earlier ones in the series?  As one goes through your
series, each erly one should not depend on the later ones.

julia

>
> > 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
> >
> >
>
>