linux-kernel - Re: [PATCH 0/7] Permit filesystem local caching and NFS superblock sharing [try #13]

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]

Date:	Wed, 30 Aug 2006 13:55:03 -0700
From:	Andrew Morton <akpm@...l.org>
To:	David Howells <dhowells@...hat.com>
Cc:	torvalds@...l.org, steved@...hat.com, trond.myklebust@....uio.no,
	linux-fsdevel@...r.kernel.org, linux-cachefs@...hat.com,
	nfsv4@...ux-nfs.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/7] Permit filesystem local caching and NFS superblock
 sharing [try #13]

On Wed, 30 Aug 2006 21:37:18 +0100
David Howells <dhowells@...hat.com> wrote:

> Andrew Morton <akpm@...l.org> wrote:
> 
> > > These patches add local caching for network filesystems such as NFS and AFS.
> > 
> > <fercrissake>
> > 
> > Not interested.  Please go learn quilt, send incremental patches.
> 
> What's quilt able to do that StGIT can't?  AFAICT from quilt's manpage, it
> can't mail incremental patches, so how does it help anyway?
> 

It was just a suggestion.  Please:

- test the patches which are presently in -mm.  I don't even know if they
  work, and we prefer to send Linus working stuff.

- Send fine-grained incremental patches.  It's OK to do complete
  replacement patchsets when the code is new, but this stuff is supposed to
  be stabilised.

  It took me quite a lot of time to extract the incremental patches out
  of try#12 and I don't want to do it again, plus it's just another step in
  which errors can be introduced.

Why incremental patches?

- So we can see what changed and don't have to re-review the whole thing

- So the recipient doesn't have to re-fix the same pile of rejects each time.

- So fixes which came in via other sources don't get lost.
-
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/