From: Christoph Hellwig <hch@infradead.org>
To: Jeff Mahoney <jeffm@jeffreymahoney.com>
Cc: Chris Mason <chris.mason@oracle.com>,
Btrfs Development List <linux-btrfs@vger.kernel.org>
Subject: Re: [patch 0/5] btrfs-progs: Create libbtrfs and package it up
Date: Fri, 13 Jun 2008 16:29:53 -0400 [thread overview]
Message-ID: <20080613202953.GA8819@infradead.org> (raw)
In-Reply-To: <20080613200906.180149089@suse.com>
On Fri, Jun 13, 2008 at 04:09:06PM -0400, Jeff Mahoney wrote:
> lib contains the objects that used to be $(COMMON_OBJS), but are now
> a full-fledged shared library with supporting includes to be installed
> in /usr/include/btrfs. Headers are also placed in lib so that patches
> indended for the kernel can also apply to the library without a lot of
> effort.
I don't think making this a public library yet is a good idea, the API
will change frequently and it'll be a pain to keep it uptodate. Just
make it an internal static library for now.
next prev parent reply other threads:[~2008-06-13 20:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 20:09 [patch 0/5] btrfs-progs: Create libbtrfs and package it up Jeff Mahoney
2008-06-13 20:09 ` [patch 1/5] btrfs-progs: convert to autotools Jeff Mahoney
2008-06-14 2:09 ` Miguel Sousa Filipe
2008-06-14 5:22 ` Jeff Mahoney
2008-06-14 6:10 ` Dongjun Shin
2008-06-14 6:38 ` Joe Peterson
2008-06-13 20:09 ` [patch 2/5] btrfs-progs: Test for sparse support in configure Jeff Mahoney
2008-06-13 20:09 ` [patch 3/5] btrfs-progs: Restructure code layout, create libbtrfs Jeff Mahoney
2008-06-13 20:09 ` [patch 4/5] btrfs-progs: Add RPM spec file support Jeff Mahoney
2008-06-13 20:09 ` [patch 5/5] btrfs-progs: Script to restructure the source as needed by patch 3 Jeff Mahoney
2008-06-13 20:29 ` Christoph Hellwig [this message]
2008-06-13 17:17 ` [patch 0/5] btrfs-progs: Create libbtrfs and package it up Jeff Mahoney
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=20080613202953.GA8819@infradead.org \
--to=hch@infradead.org \
--cc=chris.mason@oracle.com \
--cc=jeffm@jeffreymahoney.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox