All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: Chris Mason <chris.mason@oracle.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>,
	Arne Jansen <sensille@gmx.net>
Subject: Re: Btrfs progs git repo on kernel.org
Date: Thu, 27 Oct 2011 22:48:11 +0100	[thread overview]
Message-ID: <20111027214811.GL29548@carfax.org.uk> (raw)
In-Reply-To: <20111027213258.GA25582@shiny.Mikenopa.local>

[-- Attachment #1: Type: text/plain, Size: 2296 bytes --]

On Thu, Oct 27, 2011 at 05:32:58PM -0400, Chris Mason wrote:
> On Thu, Oct 27, 2011 at 04:58:54PM +0100, Hugo Mills wrote:
> > On Thu, Oct 27, 2011 at 11:27:07AM -0400, Chris Mason wrote:
> > > I've pulled in Hugo's integration tree, minus the features that were not
> > > yet in the kernel.  This also has a few small commits that I had queued
> > > up outside of the fsck work.
> > > 
> > > Hugo, many thanks for keeping up the integration tree!  Taking out the
> > > features not in the kernel meant I had to rebase it the commits, I'm
> > > sorry about that.
> > 
> >    OK, I'm sure I can cope with that. I'll just drop the patches from
> > my stack that you've already brought in, and generate a new
> > integration branch based on your master. I've got 4-5 other patches to
> > add in as well, gleaned from the mailing list and, via David Sterba,
> > from SuSE's local patches.
> > 
> >    I've also got the basis of a set of regression tests for -progs,
> > which I'll send out patches for in the next couple of days. At the
> > moment, it only tests building and snapshots, but should be relatively
> > easily extensible to the other bits of ./btrfs (although I'm not sure
> > how we can easily and repeatably test the recovery tools).
> 
> Please talk with Anand Jain on the test programs, he has been making
> scripts for xfs-tests.

   Will do, although I think we're aiming at different things. I'm
very definitely *not* attempting to test the filesystem itself with my
test harness. I just want to exercise all the bits of the userspace
tools that I can. (This was primarily triggered by the mess
surrounding the parsing of "btrfs sub snap" parameters).

> >    One other thing that's *really* needed is a new version tag, which
> > I was going to do this weekend, but it looks like you're back at the
> > helm of -progs, so I'll just whine in your general direction instead.
> 
> Definitely, fsck deserves a new version tag.

   You mean we've got to wait *that* long? ;)

   Hugo.

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
     --- "I don't like the look of it,  I tell you." "Well, stop ---     
                          looking at it, then."                          

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

  reply	other threads:[~2011-10-27 21:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-27 15:27 Btrfs progs git repo on kernel.org Chris Mason
2011-10-27 15:58 ` Hugo Mills
2011-10-27 21:32   ` Chris Mason
2011-10-27 21:48     ` Hugo Mills [this message]
2011-10-28  2:23       ` Anand Jain
2011-10-28 16:27 ` Sergei Trofimovich
2011-10-29  5:07   ` Chris Mason
2011-11-15 15:12 ` Phillip Susi

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=20111027214811.GL29548@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sensille@gmx.net \
    /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.