From: Greg KH <gregkh@linuxfoundation.org>
To: John Wyatt <jbwyatt4@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] Outreachy patches caught up on.
Date: Sat, 21 Mar 2020 07:51:34 +0100 [thread overview]
Message-ID: <20200321065134.GA849159@kroah.com> (raw)
In-Reply-To: <024f9fe964fce4a9ede1d58c87b7bb75c6a35ac2.camel@gmail.com>
On Fri, Mar 20, 2020 at 11:33:41AM -0700, John Wyatt wrote:
> On Fri, 2020-03-20 at 15:14 +0100, Greg KH wrote:
> > Hi all,
> >
> > I'm now caught up on all submitted outreachy patches that I can
> > apply.
> >
> > If you have not gotten an email from my patch system saying that your
> > patch was applied, consider it lost, and please rebase and resend it.
>
> Hi Greg,
>
> I just sent my patch in ~10 hours ago.
>
> Do I need to rebase/resend it?
>
> If I do, should I make it a v2?
>
> Apologies if you already answered this earlier in the mailing list.
Julia provided comments on what you need to do to fix up your patch,
please follow them and resend a v2.
thanks,
greg k-h
next prev parent reply other threads:[~2020-03-21 6:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 14:14 Outreachy patches caught up on Greg KH
2020-03-20 18:33 ` [Outreachy kernel] " John Wyatt
2020-03-21 6:51 ` Greg KH [this message]
2020-03-21 7:04 ` John Wyatt
2020-03-21 7:05 ` Greg KH
2020-03-21 7:26 ` John Wyatt
2020-03-21 7:41 ` Greg KH
2020-03-23 9:56 ` Sam Muhammed
2020-03-23 10:05 ` Julia Lawall
2020-03-23 10:28 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2020-03-17 14:09 Greg KH
2020-03-17 19:25 ` [Outreachy kernel] " DEEPAK VARMA
2020-03-17 19:32 ` Greg KH
2020-03-18 2:33 ` DEEPAK VARMA
2019-10-26 18:50 Greg KH
2019-10-26 18:57 ` [Outreachy kernel] " evan chime
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=20200321065134.GA849159@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jbwyatt4@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.