From: Greg KH <gregkh@suse.de>
To: Pavan Savoy <pavan_savoy@sify.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: staging-tree: to stage or not to stage
Date: Thu, 6 Jan 2011 14:07:05 -0800 [thread overview]
Message-ID: <20110106220705.GJ30799@suse.de> (raw)
In-Reply-To: <AANLkTikgHBVoPiPTXumcBn-t620=6xy+=2AaY3WYPmmY@mail.gmail.com>
On Thu, Dec 23, 2010 at 04:11:43PM +0530, Pavan Savoy wrote:
> Hi Greg,
>
> <long mail warning...>
>
> We've been having this discussion here and there, and there has been
> various opinions about what staging is,
> I've also read your mail @ http://lwn.net/Articles/285594/ on what the
> tree IS and what it is NOT.
>
> So, hoping you dispel all opinions and lay down some facts!!!
Sure, please ask specific questions and I will be glad to answer them.
I understand you are frustrated that some of your code had to be
rewritten numerous times, but that is just the nature of Linux kernel
development sorry. I'm pretty sure that you agree that the end result
is much better than the original submissions, right?
thanks,
greg k-h
prev parent reply other threads:[~2011-01-06 22:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 10:41 staging-tree: to stage or not to stage Pavan Savoy
2011-01-06 22:07 ` 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=20110106220705.GJ30799@suse.de \
--to=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavan_savoy@sify.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox