> From: Greg KH [mailto:gregkh@xxxxxxxxxxxxxxxxxxx] > Sent: Friday, January 18, 2013 1:47 PM > To: Dan Magenheimer > Cc: devel@xxxxxxxxxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; linux-mm@xxxxxxxxx; ngupta@xxxxxxxxxx; > Konrad Wilk; sjenning@xxxxxxxxxxxxxxxxxx; minchan@xxxxxxxxxx > 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@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href