From: David Sterba <dsterba@suse.cz>
To: Petr Bena <benapetr@gmail.com>
Cc: Hugo Mills <hugo@carfax.org.uk>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: New tool to recursive compress / decompress of files
Date: Wed, 25 Mar 2015 02:42:01 +0100 [thread overview]
Message-ID: <20150325014200.GC20767@twin.jikos.cz> (raw)
In-Reply-To: <CA+4EQ5cWV-HaKGnmsn73Bif-w4otyz8JD_LRHeO=-Que+cRaYg@mail.gmail.com>
On Sat, Mar 21, 2015 at 07:12:52PM +0100, Petr Bena wrote:
> I would be certainly useful if this kind of tricks were mentioned on
> https://btrfs.wiki.kernel.org/index.php/Compression or anywhere on
> wiki
There's a gap between developers (who don't want to write documentation
because they know how to do things) and users (who expect there's enough
documentaion how to do things).
We're getting better and the user queries and complaints help to close
this gap but docs are still not perfect and somebody has to find the
time to write it.
The wiki is open, I'm merging documentation updates to btrfs-progs (ie.
man pages) right away, but this still does not seem to encourage enough
people. No coding skills rquired. Would github-style of pull requests
help to improve that? Or plain mails with the portions of text that'd
go to manpages (ie. no bothering with formatting)?
next prev parent reply other threads:[~2015-03-25 1:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-21 17:56 New tool to recursive compress / decompress of files Petr Bena
2015-03-21 18:08 ` Hugo Mills
2015-03-21 18:12 ` Petr Bena
2015-03-21 18:16 ` Petr Bena
2015-03-25 1:49 ` David Sterba
2015-03-25 1:42 ` David Sterba [this message]
2015-03-21 18:22 ` Roman Mamedov
2015-03-21 18:25 ` Petr Bena
2015-03-21 18:26 ` Petr Bena
2015-03-21 19:27 ` Marc MERLIN
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=20150325014200.GC20767@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=benapetr@gmail.com \
--cc=hugo@carfax.org.uk \
--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.