From: Greg KH <gregkh@linuxfoundation.org>
To: DEEPAK VARMA <mh12gx2825@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] Outreachy patches caught up on.
Date: Tue, 17 Mar 2020 20:32:31 +0100 [thread overview]
Message-ID: <20200317193231.GA1566692@kroah.com> (raw)
In-Reply-To: <20200317192530.GB22314@deeUbuntu>
On Wed, Mar 18, 2020 at 12:55:31AM +0530, DEEPAK VARMA wrote:
> > 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.
>
> If we have a patch where the review comments by the experts were not
> implemented, but it was accepted by you, what should we do with those
> now? Would you suggest sending in a fresh patch with the comments
> implemented or a vn in continuation of the old patch?
Consider yourself lucky that I took the patch :)
You can send a follow-on patch, if the changes requested was in the
code, not the subject/changelog areas. But as my tree is not rebased,
you can't send a "please replace my old patch with this one instead"
request as that's impossible for me to do.
thanks,
greg k-h
next prev parent reply other threads:[~2020-03-17 19:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 14:09 Outreachy patches caught up on Greg KH
2020-03-17 19:25 ` [Outreachy kernel] " DEEPAK VARMA
2020-03-17 19:32 ` Greg KH [this message]
2020-03-18 2:33 ` DEEPAK VARMA
-- strict thread matches above, loose matches on Subject: below --
2020-03-20 14:14 Greg KH
2020-03-20 18:33 ` [Outreachy kernel] " John Wyatt
2020-03-21 6:51 ` Greg KH
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
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=20200317193231.GA1566692@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=mh12gx2825@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.