From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Greg KH <gregkh@linuxfoundation.org>
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 2/5] staging: zcache: rename ramster to zcache
Date: Fri, 18 Jan 2013 12:54:41 -0800 (PST) [thread overview]
Message-ID: <9d1e65ec-9a8d-4639-8825-97a2ae897f93@default> (raw)
In-Reply-To: <20130118204655.GC4788@kroah.com>
> From: Greg KH [mailto:gregkh@linuxfoundation.org]
> Sent: Friday, January 18, 2013 1:47 PM
> To: Dan Magenheimer
> Cc: devel@linuxdriverproject.org; linux-kernel@vger.kernel.org; linux-mm@kvack.org; ngupta@vflare.org;
> Konrad Wilk; sjenning@linux.vnet.ibm.com; minchan@kernel.org
> Subject: Re: [PATCH 2/5] staging: zcache: rename ramster to zcache
>
> On Thu, Jan 17, 2013 at 09:26:34AM -0800, Dan Magenheimer wrote:
> > In staging, rename ramster to zcache
> >
> > The original zcache in staging was a "demo" version, and this new zcache
> > is a significant rewrite. While certain disagreements were being resolved,
> > both "old zcache" and "new zcache" needed to reside in the staging tree
> > simultaneously. In order to minimize code change and churn, the newer
> > version of zcache was temporarily merged into the "ramster" staging driver
> > which, prior to that, had at one time heavily leveraged the older version
> > of zcache. So, recently, "new zcache" resided in the ramster directory.
> >
> > Got that? No? Sorry, temporary political compromises are rarely pretty.
> >
> > The older version of zcache is no longer being maintained and has now
> > been removed from the staging tree. So now the newer version of zcache
> > can rightfully reclaim sole possession of the name "zcache".
> >
> > This patch is simply a manual:
> >
> > # git mv drivers/staging/ramster drivers/staging/zcache
> >
> > so the actual patch diff has been left out.
> >
> > Because a git mv loses history, part of the original description of
> > the changes between "old zcache" and "new zcache" is repeated below:
>
> git mv does not loose history, it can handle it just fine.
OK will fix. Heh, apparently, you learn something wrong on the internet
("git mv loses history") every day, too. :-(
Thanks,
Dan
--
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:[~2013-01-18 20:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 17:26 [PATCH 0/5] staging: zcache: move new zcache code base from ramster Dan Magenheimer
2013-01-17 17:26 ` [PATCH 1/5] staging: ramster: disable build in anticipation of renaming Dan Magenheimer
2013-01-17 17:26 ` [PATCH 2/5] staging: zcache: rename ramster to zcache Dan Magenheimer
2013-01-18 20:46 ` Greg KH
2013-01-18 20:54 ` Dan Magenheimer [this message]
2013-01-17 17:26 ` [PATCH 3/5] staging: zcache: adjustments to config/build files due to renaming Dan Magenheimer
2013-01-17 17:26 ` [PATCH 4/5] staging: zcache: re-enable config/build of zcache after renaming Dan Magenheimer
2013-01-17 17:26 ` [PATCH 5/5] staging: zcache: fix uninitialized variable compile warning Dan Magenheimer
2013-01-18 20:46 ` [PATCH 0/5] staging: zcache: move new zcache code base from ramster Greg KH
2013-01-18 20:53 ` Dan Magenheimer
2013-01-18 21:24 [PATCH V2 " Dan Magenheimer
2013-01-18 21:24 ` [PATCH 2/5] staging: zcache: rename ramster to zcache Dan Magenheimer
2013-01-19 19:57 ` Dan Carpenter
2013-01-22 17:04 ` 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=9d1e65ec-9a8d-4639-8825-97a2ae897f93@default \
--to=dan.magenheimer@oracle.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.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