From: Rory Campbell-Lange <rory@campbell-lange.net>
To: Arne Jansen <sensille@gmx.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Fits: tool to parse stream
Date: Sat, 13 Oct 2012 09:08:57 +0100 [thread overview]
Message-ID: <20121013080857.GA1491@campbell-lange.net> (raw)
In-Reply-To: <50791203.6060406@gmx.net>
On 13/10/12, Arne Jansen (sensille@gmx.net) wrote:
> On 10/12/12 15:32, Arne Jansen wrote:
>
> > The idea of the btrfs send stream format was to generate it in a way that
> > it is easy to receive on different platforms. Thus the proposed name FITS, for
> > Filesystem Incremental Backup Stream. We should also build the tools to
> > receive the stream on different platforms.
>
> I meant to write 'Filesystem Incremental Transport Stream', but, as
> Andrey Kuzmin pointed out, the name FITS is already taken. As the
> 'Backup' slipped in somehow, FIBS might be an alternative. Any
> thoughts?
Perhaps "BTRFS Incremental Stream" or "Backup Incremental Stream" should
be considered, with the file extension ".bis".
The word "bis" is also, according to Wikipedia, "...a prefix of suffix
designating the second instance of a thing...", which seems largely
appropriate.
http://en.m.wikipedia.org/wiki/BIS
Rory
--
Rory Campbell-Lange
rory@campbell-lange.net
next prev parent reply other threads:[~2012-10-13 12:29 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 [this message]
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
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=20121013080857.GA1491@campbell-lange.net \
--to=rory@campbell-lange.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).