From: Greg KH <gregkh@linuxfoundation.org>
To: outreachy-kernel@googlegroups.com
Subject: Caught up on Outreachy patches, again.
Date: Thu, 9 Mar 2017 19:41:03 +0100 [thread overview]
Message-ID: <20170309184103.GA16032@kroah.com> (raw)
Hi all,
I've now caught up on all submitted outreachy kernel patches. Wow there
were a lot of them...
Because of the huge quantity, odds are I have missed some. So if you
have not gotten an email from my automated patch scripts saying your
patch has been applied, consider it rejected or lost. Please resend
anything that you think is ready to be merged.
thanks,
greg k-h
next reply other threads:[~2017-03-09 18:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 18:41 Greg KH [this message]
2017-03-09 18:58 ` [Outreachy kernel] Caught up on Outreachy patches, again Alison Schofield
-- strict thread matches above, loose matches on Subject: below --
2017-03-12 14:31 Greg KH
2016-10-09 15:29 Caught up on Outreachy patches again Greg KH
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=20170309184103.GA16032@kroah.com \
--to=gregkh@linuxfoundation.org \
--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.