All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anand Jain <Anand.Jain@oracle.com>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: update INSTALL file
Date: Tue, 28 Jan 2014 17:26:12 +0800	[thread overview]
Message-ID: <52E777B4.6090906@oracle.com> (raw)
In-Reply-To: <20140127182729.GE6498@twin.jikos.cz>




  Yep. I had the same opinion as well but was hesitant
  to make wide changes unless understand the backaground.
  Now would try to re-write as a whole and review will help.

Thanks, Anand

On 01/28/2014 02:27 AM, David Sterba wrote:
> On Wed, Jan 22, 2014 at 02:19:37PM +0800, Anand Jain wrote:
>> --- a/INSTALL
>> +++ b/INSTALL
>> @@ -12,7 +12,8 @@ complete:
>>   modprobe libcrc32c
>>   insmod btrfs.ko
>>
>> -The Btrfs utility programs require libuuid to build.  This can be found
>> +The Btrfs utility programs (btrfs-progs) require libattr zlib libacl
>> +e2fsprogs libblkid lzo2 to build.  This can be found
>
> The following sentence does not make sense in the context of the
> extended list, also I think that the dependencies should be listed one
> per-line so it's more clear.
>
>>   in the e2fsprogs sources, and is usually available as libuuid or
>>   e2fsprogs-devel from various distros.
>
> The whole file looks very obsolete, mentions kernel module dependencies
> as well. Not a priority, but I wouldn't mind trimming the unrelated
> information and keep just what's related to userspace, eg. how to build,
> run local tests, where to find git sources.
>

  reply	other threads:[~2014-01-28  9:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-22  6:19 [PATCH] btrfs-progs: update INSTALL file Anand Jain
2014-01-27 18:27 ` David Sterba
2014-01-28  9:26   ` Anand Jain [this message]
2014-01-27 21:21 ` Daniel Cegiełka
2014-01-27 22:47   ` Darrick J. Wong

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=52E777B4.6090906@oracle.com \
    --to=anand.jain@oracle.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.