From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: xfstests and ext4 Date: Wed, 19 Nov 2014 11:07:25 -0800 Message-ID: <20141119190725.GA6264@infradead.org> References: <20141114000216.GN28565@dastard> <20141117203804.GO23575@dastard> <20141118202818.GP23575@dastard> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Steve French , "linux-ext4@vger.kernel.org" , linux-fsdevel , fstests@vger.kernel.org To: Dave Chinner Return-path: Received: from bombadil.infradead.org ([198.137.202.9]:41376 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755342AbaKSTH1 (ORCPT ); Wed, 19 Nov 2014 14:07:27 -0500 Content-Disposition: inline In-Reply-To: <20141118202818.GP23575@dastard> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Wed, Nov 19, 2014 at 07:28:18AM +1100, Dave Chinner wrote: > No need for that. Keep the xfstests source tree on your > laptop/workstation and do all your edits there. When you've done > that, simply rsync the tree to the test VM(s) and run "make; ./check > ..." from the shell you are running in the test VM. > > That way you can manage the code multiple test VMs run from a single > source tree, all in one location, and you don't have to worry about > setting up for mail, backups, losing changes because a test machine > crash ate your recent changes, accidentally sending changes are > root, etc... Or commit them to a local git branch that you can pull from the VMs instead of the rsync. The effect is the same, though.