From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cantor2.suse.de ([195.135.220.15]:35481 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752071AbbCYBmD (ORCPT ); Tue, 24 Mar 2015 21:42:03 -0400 Date: Wed, 25 Mar 2015 02:42:01 +0100 From: David Sterba To: Petr Bena Cc: Hugo Mills , linux-btrfs Subject: Re: New tool to recursive compress / decompress of files Message-ID: <20150325014200.GC20767@twin.jikos.cz> Reply-To: dsterba@suse.cz References: <20150321180846.GE31762@carfax.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: linux-btrfs-owner@vger.kernel.org List-ID: 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)?