linux-kernel - Re: [PATCH 0/3] staging: zcache+ramster: move to new code base and re-merge

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: <20120816230817.GA14757@kroah.com>
Date:	Thu, 16 Aug 2012 16:08:17 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Dan Magenheimer <dan.magenheimer@...cle.com>
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 0/3] staging: zcache+ramster: move to new code base and
 re-merge

On Thu, Aug 16, 2012 at 03:53:11PM -0700, Dan Magenheimer wrote:
> > From: Greg KH [mailto:gregkh@...uxfoundation.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 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/