From: Theodore Tso <tytso-3s7WtUTddSA@public.gmane.org>
To: Karel Zak <kzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Eric Sandeen <sandeen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Andreas Dilger <adilger-KYPl3Ael/zSakBO8gow8eQ@public.gmane.org>,
linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
List util-linux-ng
<util-linux-ng-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] obsolete libcom-err for SuSE e2fsprogs
Date: Mon, 24 Sep 2007 08:40:36 -0400 [thread overview]
Message-ID: <20070924124035.GA4209@thunk.org> (raw)
In-Reply-To: <20070924092539.GC2819-CxBs/XhZ2BtHjqfyn1fVYA@public.gmane.org>
On Mon, Sep 24, 2007 at 11:25:39AM +0200, Karel Zak wrote:
> >
> > Nope, there isn't much rationale unless we also split out fsck, so
>
> util-linux-ng is open for fsck :-)
It's something I'm considering, but at the moment I've got some higher
priority (ext4) work that I'm focusing on.
What would you think about moving libblkid and the libdisk from
xfsprogs into util-linux-ng? That's things that I've been batting
around doing, although that means we end up moving more libraries that
distros would probably want separated into different packages into
util-linux-ng....
- Ted
next prev parent reply other threads:[~2007-09-24 12:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 6:14 [PATCH] obsolete libcom-err for SuSE e2fsprogs Andreas Dilger
2007-09-20 1:41 ` Eric Sandeen
2007-09-20 5:09 ` Andreas Dilger
2007-09-20 20:22 ` Eric Sandeen
2007-09-20 20:42 ` Andreas Dilger
2007-09-20 21:54 ` Theodore Tso
2007-09-24 9:25 ` Karel Zak
[not found] ` <20070924092539.GC2819-CxBs/XhZ2BtHjqfyn1fVYA@public.gmane.org>
2007-09-24 12:40 ` Theodore Tso [this message]
[not found] ` <20070924124035.GA4209-AKGzg7BKzIDYtjvyW6yDsg@public.gmane.org>
2007-09-24 13:16 ` Eric Sandeen
2007-09-25 9:14 ` Karel Zak
2007-09-25 10:11 ` Kay Sievers
2007-09-25 12:34 ` Karel Zak
2007-09-25 15:20 ` Theodore Tso
[not found] ` <20070925123454.GE2806-CxBs/XhZ2BtHjqfyn1fVYA@public.gmane.org>
2007-09-25 20:25 ` Kay Sievers
2007-09-25 20:57 ` Karel Zak
2007-09-25 21:35 ` Christoph Hellwig
2007-09-25 9:27 ` Matthias Koenig
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=20070924124035.GA4209@thunk.org \
--to=tytso-3s7wtutddsa@public.gmane.org \
--cc=adilger-KYPl3Ael/zSakBO8gow8eQ@public.gmane.org \
--cc=kzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sandeen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=util-linux-ng-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).