From: Adrian Bunk <bunk@stusta.de>
To: Takashi Sato <sho@bsd.tnes.nec.co.jp>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
linux-kernel@vger.kernel.org, Ext2-devel@lists.sourceforge.net
Subject: Re: [Ext2-devel] [RFC][15/21]e2fsprogs modify variables for bitmap to exceed 2G
Date: Mon, 17 Apr 2006 14:48:07 +0200 [thread overview]
Message-ID: <20060417124807.GB7429@stusta.de> (raw)
In-Reply-To: <020501c6621a$bf158c50$4168010a@bsd.tnes.nec.co.jp>
On Mon, Apr 17, 2006 at 09:30:39PM +0900, Takashi Sato wrote:
> Thank you for your comment, Ted.
>
> >Generalized NACK. We can't just blindly change function signatures of
> >pre-existing functions in libext2fs, since this breaks the ABI with
> >pre-existing applications linked with current shared libraries of
> >libext2fs.
>
> Though I checked if there are any commands which use the following
> functions in RHEL4, no such commands were found except in e2fsprogs
> itself.
>...
> ext2fs_test_block_bitmap()
>...
Used by e2undel [1].
> So I think changing these function signatures does not break the ABI
> practically. Am I missing something?
>
> Cheers, sho
cu
Adrian
[1] http://e2undel.sourceforge.net/
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-04-17 12:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 7:12 [RFC][15/21]e2fsprogs modify variables for bitmap to exceed 2G sho
2006-04-13 16:20 ` [Ext2-devel] " Theodore Ts'o
2006-04-17 12:30 ` Takashi Sato
2006-04-17 12:48 ` Adrian Bunk [this message]
2006-04-18 4:37 ` Takashi Sato
2006-04-17 13:01 ` Arjan van de Ven
2006-04-18 7:45 ` Takashi Sato
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=20060417124807.GB7429@stusta.de \
--to=bunk@stusta.de \
--cc=Ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sho@bsd.tnes.nec.co.jp \
--cc=tytso@mit.edu \
/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