From: Arne Jansen <sensille@gmx.net>
To: Chris Mason <chris.mason@fusionio.com>,
David Sterba <dave@jikos.cz>,
Rory Campbell-Lange <rory@campbell-lange.net>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Fits: tool to parse stream
Date: Mon, 22 Oct 2012 08:41:49 +0200 [thread overview]
Message-ID: <5084EAAD.4090806@gmx.net> (raw)
In-Reply-To: <20121015143222.GA31310@shiny>
On 15.10.2012 16:32, Chris Mason wrote:
> On Sat, Oct 13, 2012 at 09:41:28AM -0600, David Sterba wrote:
>> On Sat, Oct 13, 2012 at 09:08:57AM +0100, Rory Campbell-Lange wrote:
>>> Perhaps "BTRFS Incremental Stream" or "Backup Incremental Stream" should
>>> be considered, with the file extension ".bis".
>>
>> From the brainstorming we had about the name, the intention behind the
>> stream is to be filesystem independent.
>>
>> So this might be named FIS with .fis extension, that is not far from the
>> proposed name. However, this hasn't been approved by the Slang committee
>> yet :)
>
> urbandictionary has some entries for fis, although I'm not really sure
> that matters. .fs is still my favorite, or .fss if you want to have the
> word stream in there.
We finally settled on 'far', Filesystem Agnostic Replication.
-Arne
>
> The stream parser is really cool though, thanks Arne.
>
> -chris
>
next prev parent reply other threads:[~2012-10-22 6:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 13:32 [PATCH] Fits: tool to parse stream Arne Jansen
[not found] ` <CANvN+e=YQ2HG2sDrhy-WqfsnSXbT=LFA18Wj-FZK6NC-gMyeAA@mail.gmail.com>
2012-10-12 15:22 ` Arne Jansen
2012-10-13 7:02 ` Arne Jansen
2012-10-13 8:08 ` Rory Campbell-Lange
2012-10-13 15:41 ` David Sterba
2012-10-15 14:32 ` Chris Mason
2012-10-15 20:11 ` Alex Lyakas
2012-10-22 6:41 ` Arne Jansen [this message]
2012-10-22 16:21 ` Chris Mason
2012-10-13 11:23 ` Hugo Mills
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=5084EAAD.4090806@gmx.net \
--to=sensille@gmx.net \
--cc=chris.mason@fusionio.com \
--cc=dave@jikos.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=rory@campbell-lange.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.