From: Arvin Schnell <aschnell@suse.de>
To: Ilya Dryomov <idryomov@gmail.com>
Cc: Mark Fasheh <mfasheh@suse.de>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/3] btrfs-progs: libify some parts of btrfs-progs
Date: Tue, 15 Jan 2013 14:26:45 +0100 [thread overview]
Message-ID: <20130115132645.GA10431@suse.de> (raw)
In-Reply-To: <20130115124650.GA2040@zambezi.lan>
On Tue, Jan 15, 2013 at 02:46:50PM +0200, Ilya Dryomov wrote:
> On Mon, Jan 14, 2013 at 03:18:14PM +0100, Arvin Schnell wrote:
> >
> > Hi,
> >
> > please find attached a patch to make the new libbtrfs usable from
> > C++ (at least for the parts snapper will likely need).
> Why exactly do we need this in a non-header file?
Oh, that's clearly a mistake. Thanks for noticing.
Regards,
Arvin
--
Arvin Schnell, <aschnell@suse.de>
Senior Software Engineer, Research & Development
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
Maxfeldstraße 5
90409 Nürnberg
Germany
next prev parent reply other threads:[~2013-01-15 13:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 21:41 [PATCH 0/3] btrfs-progs: better support for external users of send Mark Fasheh
2013-01-08 21:41 ` [PATCH 1/3] btrfs-progs: Add support for BTRFS_SEND_FLAG_NO_FILE_DATA Mark Fasheh
2013-01-08 21:41 ` [PATCH 2/3] btrfs-progs: libify some parts of btrfs-progs Mark Fasheh
2013-01-11 9:31 ` Anand Jain
2013-01-11 23:00 ` Mark Fasheh
2013-01-14 3:42 ` Anand Jain
2013-01-14 18:16 ` Mark Fasheh
2013-01-14 22:27 ` Mark Fasheh
2013-01-14 3:43 ` Anand Jain
2013-01-14 18:10 ` Mark Fasheh
2013-01-15 8:06 ` Anand Jain
2013-01-16 22:11 ` Mark Fasheh
2013-01-14 14:18 ` Arvin Schnell
2013-01-14 18:14 ` Mark Fasheh
2013-01-14 22:26 ` Arvin Schnell
2013-01-15 12:46 ` Ilya Dryomov
2013-01-15 13:26 ` Arvin Schnell [this message]
2013-01-08 21:41 ` [PATCH 3/3] btrfs-progs: add send-test Mark Fasheh
2013-01-11 9:28 ` Anand Jain
2013-01-11 23:02 ` Mark Fasheh
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=20130115132645.GA10431@suse.de \
--to=aschnell@suse.de \
--cc=idryomov@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mfasheh@suse.de \
/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.