All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: Btrfs mailing list <linux-btrfs@vger.kernel.org>
Cc: Chris Mason <chris.mason@oracle.com>
Subject: New integration branch for btrfs-progs
Date: Mon, 31 Oct 2011 08:40:11 +0000	[thread overview]
Message-ID: <20111031084011.GU29548@carfax.org.uk> (raw)

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

   All - 

   I've put together a new integration branch based on Chris's new
master. This includes the userspace patches for qgroups, restriper,
and Josef's restore utility, plus a bunch of other things with mostly
minor impact. The shortlog is attached at the end of this email.

   As always, it's available from:

http://git.darksatanic.net/repo/btrfs-progs-unstable.git/  integration-20111030

and the gitweb address is 

http://git.darksatanic.net/cgi/gitweb.cgi?p=btrfs-progs-unstable.git;a=summary

   Could I ask that if anyone is writing patches to go in btrfs-progs,
that you base them on Chris's master (or on my for-chris branch, when
it exists). Basing patches on the integration-* branches is a bad
idea, because they get thrown away each time I make a new one, and
it's just more work for me to rebase the patches.

   Chris -- Don't pull from this directly, I'll be sending you a pull
request for a subset of the patches in a few days.

   Hugo.

Arne Jansen (1):
      btrfs-progs: add qgroup commands

Chris Mason (5):
      btrfs-progs: fixup is_mounted checks
      restore: deal with holes and set i_size correctly
      btrfs-debug-tree: add -r option to print only the roots
      btrfs-progs: add a utility to corrupt a single block
      btrfs-progs: remove old debugging statement

David Sterba (3):
      btrfs-progs: ignore -a option in mkfs
      btrfs-progs: ignore deleted loop devices
      btrfs-progs: pass correct build option for pthreads

Goffredo Baroncelli (9):
      Add the --force option.
      mkfs.btrfs man page: document the --force option.
      Ignore the error ENXIO and ENOMEDIUM during a devs scan
      Add info for the commands.
      Add the header/footer/introduction of the man page.
      helpextract: tool to extract the info for the help from the source.
      Update the makefile for generating the man page.
      Show the help messages from the info in the comment.
      Update the makefile for generating the help messages.

Hugo Mills (2):
      Regression tests
      Fix sub snap parameter handling

Ilya Dryomov (1):
      Btrfs-progs: add restriper commands

Josef Bacik (1):
      btrfs-progs: add a recovery utility to pull files from damanged filesystems

-- 
=== 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
   --- We are all lying in the gutter,  but some of us are looking ---   
                              at the stars.                              

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

             reply	other threads:[~2011-10-31  8:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-31  8:40 Hugo Mills [this message]
2011-10-31 14:20 ` New integration branch for btrfs-progs David Sterba

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=20111031084011.GU29548@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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.