linux-kernel - Re: Re: [PATCH 00/22][RFC] Unionfs: Stackable Namespace Unification Filesystem

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:	Mon, 4 Sep 2006 14:01:41 +0300
From:	"Pekka Enberg" <penberg@...helsinki.fi>
To:	"Josef Sipek" <jsipek@....cs.sunysb.edu>
Cc:	"Jan Engelhardt" <jengelh@...ux01.gwdg.de>,
	"Stephen Rothwell" <sfr@...b.auug.org.au>,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	hch@...radead.org, akpm@...l.org, viro@....linux.org.uk
Subject: Re: Re: [PATCH 00/22][RFC] Unionfs: Stackable Namespace Unification Filesystem

On 9/3/06, Josef Sipek <jsipek@....cs.sunysb.edu> wrote:
> I think you misunderstood my comment. What I meant to say was that there is
> _no way_ you can compile a filesystem that has only dentry ops but not
> superblock ops - this would happen if you tried to bisect and you landed
> half way in the series of commits for the filesystem. For the _initial_
> commit one cset makes sense. For subsequent fixes one commit per fix is the
> only logical thing to do.

Reorder the patches so that Makefile and Kconfig changes come last and
git bisect will work just fine.

-- 
VGER BF report: H 0
-
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/