All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Disseldorp <ddiss@suse.de>
To: Pavel Shilovsky <pshilovsky@samba.org>
Cc: linux-cifs <linux-cifs@vger.kernel.org>,
	samba-technical <samba-technical@lists.samba.org>,
	Steve French <smfrench@gmail.com>
Subject: Re: CIFS module build verification system
Date: Wed, 20 Aug 2014 11:20:04 +0200	[thread overview]
Message-ID: <20140820112004.66b760fc@plati.site> (raw)
In-Reply-To: <CAKywueTMGq3tmf5fo5aWPUA888TgiKWHyRH=hQxHjRQ3in5gUQ@mail.gmail.com>

On Wed, 20 Aug 2014 11:32:59 +0400, Pavel Shilovsky wrote:

...
> > The git repo for build verification system scripts:
> > http://git.altlinux.org/people/piastry/public/?p=cifs-tests.git;a=summary
> >
> > The git repo for patched Cthon tests (merged by Steve Dickson into his tree):
> > http://git.altlinux.org/people/piastry/public/?p=cthon04.git;a=summary
> >
> > The git repo for patched XFS tests:
> > http://git.altlinux.org/people/piastry/public/?p=xfstests.git;a=summary
> 
> Hi Steve, David,
> 
> Thank you for your notes and suggestions!
> 
> Do you understand right that I can squash David's commit (started with
> "SQUASH") into my patch?

Sure, go for it.

> Not sure about group file. CIFS (as NFS) doesn't have it's own tests
> now. Do you mean to add "test/cifs" directory with an empty (except a
> commented header) group file inside (to let us add cifs specific tests
> in future)?

My mistake, I thought the generic tests could be regrouped
per-filesystem. An empty template would be fine.

Cheers, David

  reply	other threads:[~2014-08-20  9:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-18 17:46 CIFS module build verification system Pavel Shilovsky
     [not found] ` <CAKywueRrd4ivRgyqkkYFVL47D-B4FwxyALg2xraQkybucVyeog-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-19  5:08   ` Steve French
2014-08-20  7:32   ` Pavel Shilovsky
2014-08-20  9:20     ` David Disseldorp [this message]
     [not found]       ` <20140820112004.66b760fc-k1XZOR0ctBLN0uC3ymp8PA@public.gmane.org>
2014-08-22 13:49         ` David Disseldorp
     [not found]           ` <20140822154915.3aa69c8e-k1XZOR0ctBLN0uC3ymp8PA@public.gmane.org>
2014-08-22 15:04             ` Pavel Shilovsky
     [not found]               ` <0B60D06C-4C5C-4A24-8007-BACF8533AF71-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-08-22 15:17                 ` David Disseldorp
2014-08-19 15:28 ` David Disseldorp

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=20140820112004.66b760fc@plati.site \
    --to=ddiss@suse.de \
    --cc=linux-cifs@vger.kernel.org \
    --cc=pshilovsky@samba.org \
    --cc=samba-technical@lists.samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.