All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: SIMRAN SINGHAL <singhalsimran0@gmail.com>
Cc: outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [Outreachy kernel] Re: Caught up on Outreachy patches
Date: Sat, 25 Feb 2017 09:01:20 +0100	[thread overview]
Message-ID: <20170225080120.GA2054@kroah.com> (raw)
In-Reply-To: <605876fe-cfb0-4389-9ca9-aa88a3b4e1ea@googlegroups.com>

On Fri, Feb 24, 2017 at 12:35:58PM -0800, SIMRAN SINGHAL wrote:
> 
> 
> On Friday, February 24, 2017 at 11:23:23 PM UTC+5:30, gregkh wrote:
> 
>     Hi all,
> 
>     I've now caught up on all submitted outreachy kernel patches.
> 
>     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.
> 
> 
> � � Greg, as for some of my patches I didn't get reply.
> � � So, now how am I supposed to send them i.e as next version
> � � of that patch or as a completely new patch.

Very odd quoting style, please fix up your email client to do this
properly.

Resend anything I missed as a new version of the patch, saying you have
fixed up whatever kept it from being accepted the first time (if I had
commented on it), or just a 'resend' if I happened to miss it.

But first rebase your patches on my staging-testing branch to ensure
that they do work properly, otherwise you are just wasting time redoing
something I will have to reject again :)

> � � And those patches also include some patches which are acked by�
> � � Julia, so sending them as completely new patch seems pointless.

Nope, that's just how it goes, but keep Julia's ack on it when you
resend.

> � � So, I request you to please explain how we are supposed to send them
> � � and sorry for asking this, but can you please explain the reason of, if
> � � those patches are present in the mailing list then why you are calling
> � � them lost.

I don't know, I need specifics here.  Did I say something about them, or
just ignore them completly?  Did I say something like "redo all of your
outstanding patches"?  Remember, I get over 1000 emails a day, and just
had to review over 500 patches submitted for the staging subsystem in
the past 5 days.  I can't remember anything specifically, and neither
could anyone else with that kind of workload :)

thanks,

greg k-h


      parent reply	other threads:[~2017-02-25  8:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-24 17:53 Caught up on Outreachy patches Greg KH
2017-02-24 20:35 ` SIMRAN SINGHAL
2017-02-24 20:48   ` [Outreachy kernel] " Julia Lawall
2017-02-24 20:54     ` SIMRAN SINGHAL
2017-02-24 21:05       ` Julia Lawall
2017-02-25  8:01   ` Greg KH [this message]

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=20170225080120.GA2054@kroah.com \
    --to=greg@kroah.com \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=singhalsimran0@gmail.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.