From: Greg KH <gregkh@linuxfoundation.org>
To: outreachy-kernel@googlegroups.com
Subject: All caught up on submitted patches!
Date: Fri, 11 Mar 2016 14:36:06 -0800 [thread overview]
Message-ID: <20160311223606.GA8018@kroah.com> (raw)
Hi all,
I've dug myself out from the huge number of submitted patches now. For
some reason this feels like we have more submitted this time than any
other time before, which is a good thing overall, nice job.
If you haven't gotten an email from me about why I rejected a patch, or
from my patch system saying your patch was accepted, assume it is lost.
Rebase your tree against my staging-testing branch of staging.git,
refresh your patches, and resend them.
thanks,
greg k-h
reply other threads:[~2016-03-11 22:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160311223606.GA8018@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.