From: gregkh@linuxfoundation.org (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: staging-testing branch
Date: Tue, 28 Feb 2017 06:26:57 +0100 [thread overview]
Message-ID: <20170228052657.GB14061@kroah.com> (raw)
In-Reply-To: <20170228003737.GA18185@eros>
On Tue, Feb 28, 2017 at 11:37:37AM +1100, Tobin C. Harding wrote:
> Greg
>
> Thanks for your unfathomable patience dealing with kernel newbies. I
> have a small suggestion, in a most humble manner.
>
> It seems that when patches don't apply the response is not
> automated, if it is possible within your system to automate checking
> if a patch actually applies would it be beneficial to point the patch
> submitter towards tracking remote branches (i.e are they basing their
> patches on on your staging-testing branch).
Normally my response is automated, and staging-testing doesn't get
abused like it currently is right now. But we are in the middle of both
the merge window, and the Outreachy intern application process, so it's
a mess. Normally during the merge window I do not touch any patches, so
things back up for 2 weeks. But due to Outreachy happening right now,
that's not very fair to the applicants, so I'm queueing up patches in
staging-testing at the moment to give them a chance to get things
accepted.
And because I'm taking Outreachy patches, I'm taking all other staging
patches as well, to keep from playing favorites with just that limited
group.
So, it's messy, and not normal (happens only once a year or so). So you
can just wait another week to do any staging patches, or just live with
the mess for a few more days until my "normal" branches open up :)
Hope this helps,
greg k-h
next prev parent reply other threads:[~2017-02-28 5:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 0:37 staging-testing branch Tobin C. Harding
2017-02-28 5:26 ` Greg KH [this message]
2017-02-28 8:53 ` Tobin C. Harding
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=20170228052657.GB14061@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).