From: Greg KH <gregkh@linuxfoundation.org>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: devel@linuxdriverproject.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, ngupta@vflare.org,
Konrad Wilk <konrad.wilk@oracle.com>,
sjenning@linux.vnet.ibm.com, minchan@kernel.org
Subject: Re: [PATCH 0/3] staging: zcache+ramster: move to new code base and re-merge
Date: Thu, 16 Aug 2012 16:08:17 -0700 [thread overview]
Message-ID: <20120816230817.GA14757@kroah.com> (raw)
In-Reply-To: <9f2da295-4164-4e95-bbe8-bd234307b83c@default>
On Thu, Aug 16, 2012 at 03:53:11PM -0700, Dan Magenheimer wrote:
> > From: Greg KH [mailto:gregkh@linuxfoundation.org]
> > Subject: Re: [PATCH 0/3] staging: zcache+ramster: move to new code base and re-merge
> >
> > On Thu, Aug 16, 2012 at 03:31:30PM -0700, Dan Magenheimer wrote:
> > > Greg, please pull for staging-next.
> >
> > Pull what?
>
> Doh! Sorry, I did that once before and used the same template for the
> message. Silly me, I meant please apply. Will try again when my
> head isn't fried. :-(
>
> > You sent patches, in a format that I can't even apply.
> > Consider this email thread deleted :(
>
> Huh? Can you explain more? I used git format-patch and git-email
> just as for previous patches and even checked the emails with
> a trial send to myself. What is un-apply-able?
Your first patch, with no patch description, and no signed-off-by line.
Come on, you know better...
On a larger note, I _really_ don't want a set of 'delete and then add it
back' set of patches. That destroys all of the work that people had
done up until now on the code base.
I understand your need, and want, to start fresh, but you still need to
abide with the "evolve over time" model here. Surely there is some path
from the old to the new codebase that you can find?
Also, I'd like to get some agreement from everyone else involved here,
that this is what they all agree is the correct way forward. I don't
think we have that agreement yet, right?
greg k-h
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-08-16 23:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 22:31 [PATCH 0/3] staging: zcache+ramster: move to new code base and re-merge Dan Magenheimer
2012-08-16 22:31 ` [PATCH 1/3] Remove old zcache and ramster staging drivers to prep for new code base Dan Magenheimer
2012-08-16 22:31 ` [PATCH 2/3] Move to new zcache codebase Dan Magenheimer
2012-08-16 22:31 ` [PATCH 3/3] Move to new codebase for ramster, re-merged with " Dan Magenheimer
2012-08-16 22:48 ` [PATCH 0/3] staging: zcache+ramster: move to new code base and re-merge Greg KH
2012-08-16 22:53 ` Dan Magenheimer
2012-08-16 23:08 ` Greg KH [this message]
2012-08-17 0:19 ` Dan Magenheimer
2012-08-17 22:32 ` Seth Jennings
2012-08-18 19:10 ` Dan Magenheimer
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=20120816230817.GA14757@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dan.magenheimer@oracle.com \
--cc=devel@linuxdriverproject.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=sjenning@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).