On Wed, Jul 23, 2008 at 11:13 PM, Sasha Khapyorsky [EMAIL PROTECTED] wrote:
On 23:04 Wed 23 Jul , Hal Rosenstock wrote:
On Wed, Jul 23, 2008 at 10:32 PM, Sasha Khapyorsky [EMAIL PROTECTED] wrote:
On 22:19 Wed 23 Jul , Hal Rosenstock wrote:
Are you saying
it's going to work with
On 09:59 Mon 28 Jul , Hal Rosenstock wrote:
Anyway I see this issue as pretty minor. It is fixed now
Is the version in libibmad.map updated now ?
It is symbol versioning, not a library.
and will appear in next tarball release.
What is your policy for updating the various versions
On Mon, Jul 28, 2008 at 12:52 PM, Sasha Khapyorsky [EMAIL PROTECTED] wrote:
On 09:59 Mon 28 Jul , Hal Rosenstock wrote:
Anyway I see this issue as pretty minor. It is fixed now
Is the version in libibmad.map updated now ?
It is symbol versioning, not a library.
and will appear in
Hi Hal,
On 05:42 Thu 10 Jul , Hal Rosenstock wrote:
Also, what about backward compatibility with apps built with the
previous version of these libraries ?
What sort of compatibility problem can we expect?
Sasha
___
general mailing list
Hi Peter,
On 15:15 Mon 14 Jul , Peter Kjellstrom wrote:
Am I understanding this correctly, you posted tarball.x.y.z.tar.gz and at a
later time modified it but left the old name? If so please don't.
No, it is exactly what I didn't want to do.
It's very
nasty to handle situations
Sasha,
On Wed, Jul 23, 2008 at 7:55 PM, Sasha Khapyorsky [EMAIL PROTECTED] wrote:
Hi Hal,
On 05:42 Thu 10 Jul , Hal Rosenstock wrote:
Also, what about backward compatibility with apps built with the
previous version of these libraries ?
What sort of compatibility problem can we
On 22:19 Wed 23 Jul , Hal Rosenstock wrote:
Are you saying
it's going to work with those changes if the APIs are used ?
func(void *p) was changed to func(const void *p), why not?
Sasha
___
general mailing list
general@lists.openfabrics.org
On Wed, Jul 23, 2008 at 10:32 PM, Sasha Khapyorsky [EMAIL PROTECTED] wrote:
On 22:19 Wed 23 Jul , Hal Rosenstock wrote:
Are you saying
it's going to work with those changes if the APIs are used ?
func(void *p) was changed to func(const void *p), why not?
Not that one; we already
On 23:04 Wed 23 Jul , Hal Rosenstock wrote:
On Wed, Jul 23, 2008 at 10:32 PM, Sasha Khapyorsky [EMAIL PROTECTED] wrote:
On 22:19 Wed 23 Jul , Hal Rosenstock wrote:
Are you saying
it's going to work with those changes if the APIs are used ?
func(void *p) was changed to
On Wednesday 09 July 2008, Sasha Khapyorsky wrote:
On 13:22 Wed 09 Jul , Hal Rosenstock wrote:
...
Is it
just the *.ver file or also the version in the *.map file ?
It is just *.ver file, *.map is symbol versioning - there were additions,
no changes in existing functions API.
this
On Thu, 2008-07-10 at 00:17 +0300, Sasha Khapyorsky wrote:
On 13:53 Wed 09 Jul , Hal Rosenstock wrote:
It is just *.ver file, *.map is symbol versioning - there were additions,
no changes in existing functions API.
Isn't that needed too when APIs are added ?
I don't think.
On Wed, 2008-07-09 at 22:05 +0300, Sasha Khapyorsky wrote:
On 11:57 Wed 09 Jul , Hal Rosenstock wrote:
891c907cf7fb56191c1cd4224608ef63 libibmad-1.2.1.tar.gz
There have been API additions and changes in the libraries since last
release. Although the tarball versions have changed,
On Wed, 2008-07-09 at 23:46 +0300, Sasha Khapyorsky wrote:
On 13:22 Wed 09 Jul , Hal Rosenstock wrote:
Thanks. Is it just libibmad or was it also libibumad as well ?
No API related changes were in libibumad.
Is it
just the *.ver file or also the version in the *.map file ?
It
On 13:53 Wed 09 Jul , Hal Rosenstock wrote:
It is just *.ver file, *.map is symbol versioning - there were additions,
no changes in existing functions API.
Isn't that needed too when APIs are added ?
I don't think.
Also, some existing
functions had minor parameter changes (like
14 matches
Mail list logo
