From: Dave Chinner <david@fromorbit.com>
To: Steve French <smfrench@gmail.com>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
fstests@vger.kernel.org
Subject: Re: xfstests and ext4
Date: Wed, 19 Nov 2014 07:28:18 +1100 [thread overview]
Message-ID: <20141118202818.GP23575@dastard> (raw)
In-Reply-To: <CAH2r5mti8hVXqmKu9kJg4Xk=5nkESCAQys1BFXhR6JSDVHOTEA@mail.gmail.com>
On Mon, Nov 17, 2014 at 08:35:39PM -0600, Steve French wrote:
> On Mon, Nov 17, 2014 at 2:38 PM, Dave Chinner <david@fromorbit.com> wrote:
>
> > the other as a base64 encoded attachment so can't be quoted and
> > replied to easily. In future, can you send patches as separate
> > emails according to:
>
> Yes. WIll do. It is a pain in test VMs to setup git with gmail two
> phase authentication
> but doable if I set it up to send mail from a different host.
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...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2014-11-18 20:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 23:38 xfstests and ext4 Steve French
2014-11-14 0:02 ` Dave Chinner
2014-11-14 1:20 ` Steve French
2014-11-17 20:38 ` Dave Chinner
2014-11-18 2:35 ` Steve French
2014-11-18 20:28 ` Dave Chinner [this message]
2014-11-19 19:07 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141118202818.GP23575@dastard \
--to=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=smfrench@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).