lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9d1e65ec-9a8d-4639-8825-97a2ae897f93@default>
Date:	Fri, 18 Jan 2013 12:54:41 -0800 (PST)
From:	Dan Magenheimer <dan.magenheimer@...cle.com>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	devel@...uxdriverproject.org, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org, ngupta@...are.org,
	Konrad Wilk <konrad.wilk@...cle.com>,
	sjenning@...ux.vnet.ibm.com, minchan@...nel.org
Subject: RE: [PATCH 2/5] staging: zcache: rename ramster to zcache

> From: Greg KH [mailto:gregkh@...uxfoundation.org]
> Sent: Friday, January 18, 2013 1:47 PM
> To: Dan Magenheimer
> Cc: devel@...uxdriverproject.org; linux-kernel@...r.kernel.org; linux-mm@...ck.org; ngupta@...are.org;
> Konrad Wilk; sjenning@...ux.vnet.ibm.com; minchan@...nel.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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ