On 09/30/2006 01:26 PM, [EMAIL PROTECTED] wrote:
Author: mturk
Date: Sat Sep 30 04:26:26 2006
New Revision: 451582
URL: http://svn.apache.org/viewvc?view=revrev=451582
Log:
Move new struct member to the end of the struct,
so we can keep the compatibility.
Sorry for nitpicking, but I am
Ruediger Pluem wrote:
URL: http://svn.apache.org/viewvc?view=revrev=451582
Log:
Move new struct member to the end of the struct,
so we can keep the compatibility.
Sorry for nitpicking, but I am still missing the minor bump.
There was no 2.3 releases, so no need for version bump.
Regards,
Mladen Turk wrote:
Ruediger Pluem wrote:
URL: http://svn.apache.org/viewvc?view=revrev=451582
Log:
Move new struct member to the end of the struct,
so we can keep the compatibility.
Sorry for nitpicking, but I am still missing the minor bump.
There was no 2.3 releases, so no need for
Paul Querna wrote:
Mladen Turk wrote:
Ruediger Pluem wrote:
URL: http://svn.apache.org/viewvc?view=revrev=451582
Log:
Move new struct member to the end of the struct,
so we can keep the compatibility.
Sorry for nitpicking, but I am still missing the minor bump.
There was no 2.3
Mladen Turk wrote:
But the trunk is usually build as is with all custom modules.
What's the point of it if we need to preserve backward compatibility.
(For what version, SVN head from DD/MM/ or what).
When the first version gets tagged from trunk, then we can have a MMN.
Until then, the
Paul Querna wrote:
Mladen Turk wrote:
But the trunk is usually build as is with all custom modules.
What's the point of it if we need to preserve backward compatibility.
(For what version, SVN head from DD/MM/ or what).
When the first version gets tagged from trunk, then we can have a MMN.
