All of lore.kernel.org
 help / color / mirror / Atom feed
From: Moviuro <moviuro@gmail.com>
To: dsterba@suse.cz, Moviuro <moviuro@gmail.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs-progs and btrfs(8) inconsistencies
Date: Wed, 9 Mar 2016 11:02:31 +0100	[thread overview]
Message-ID: <CAM=f9=X2pRjyC1H3799WmkuZ=7DSLMNnFmv4T30TcZ2VKUg_uA@mail.gmail.com> (raw)
In-Reply-To: <20160308160244.GF30625@twin.jikos.cz>

Don't hesitate to drop an email here (with your Github account
name...) to get invited into the Github group. That's because you
can't ask to join a group on GitHub.
At the moment, kdave and myself are administrators of the said group
(https://github.com/btrfs8-revamp). I'm sure we can nominate David
too, once he joined ;-)

PS: I really didn't expect my first mail to cause this movement, I'm
glad it took this shape!

      reply	other threads:[~2016-03-09 10:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-03 21:54 btrfs-progs and btrfs(8) inconsistencies Moviuro
2016-02-04  1:33 ` Qu Wenruo
2016-02-04  8:57   ` Moviuro
2016-02-04  9:15     ` Qu Wenruo
2016-02-04 10:14     ` Martin Steigerwald
2016-02-04 12:04       ` Moviuro
2016-02-04 12:53       ` Austin S. Hemmelgarn
2016-02-04 19:40         ` Chris Murphy
2016-02-04 20:19           ` Austin S. Hemmelgarn
2016-02-04 20:40             ` Moviuro
2016-02-05 13:04               ` Austin S. Hemmelgarn
2016-02-04 17:17   ` Goffredo Baroncelli
2016-02-04 19:48     ` Hugo Mills
2016-02-04 20:10     ` Chris Murphy
2016-02-04 18:22 ` Chris Murphy
2016-02-05  3:11 ` Anand Jain
2016-02-05 12:59   ` Austin S. Hemmelgarn
2016-02-06 21:35   ` Chris Murphy
2016-02-07 10:07   ` Qu Wenruo
2016-02-07 20:26     ` Goffredo Baroncelli
2016-03-08 16:02 ` David Sterba
2016-03-09 10:02   ` Moviuro [this message]

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='CAM=f9=X2pRjyC1H3799WmkuZ=7DSLMNnFmv4T30TcZ2VKUg_uA@mail.gmail.com' \
    --to=moviuro@gmail.com \
    --cc=dsterba@suse.cz \
    --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.