2010/6/8 Martin Paljak :
> On Jun 7, 2010, at 13:18 , Jean-Michel Pouré - GOOZE wrote:
>> I don't know how 0.11.14 and 0.12.0 will co-exist in Debian SID or any
>> other GNU/Linux distribution. If they do, bravo! After having to explain
>> how to remove OpenCT, now I will have to explain Gooze user
On Jun 7, 2010, at 13:18 , Jean-Michel Pouré - GOOZE wrote:
> I see a lot of efforts in SVN, merging OpenSC trunk into the branch
> named releases/0.11.14.
It is not merging trunk, it is picking critical and isolated bugs that have
been fixed in trunk into the 0.11 tree, so that it could be a drop
On Mon, 2010-06-07 at 21:53 +0200, Jean-Michel Pouré - GOOZE wrote:
>
> > trunk is incompatible ABI and API wise with 0.11.* so it can't
> > be merged without breaking ABI and API. the plan is to create
> > a new 0.12.0 release sometime soon from trunk, as far as I know.
I don't know how 0.11.14
On Mon, 2010-06-07 at 21:43 +0200, Andreas Jellinghaus wrote:
> some urgent bugs are fixed in a new 0.11.* release, with those
> important bug fixes only.
Okay.
> trunk is incompatible ABI and API wise with 0.11.* so it can't
> be merged without breaking ABI and API. the plan is to create
> a new
you seem to be confused: noone is merging trunk into 0.11.4.
for 0.11.* there is maintanence only:
some urgent bugs are fixed in a new 0.11.* release, with those
important bug fixes only.
trunk is incompatible ABI and API wise with 0.11.* so it can't
be merged without breaking ABI and API. the pl
Dear all,
I see a lot of efforts in SVN, merging OpenSC trunk into the branch
named releases/0.11.14.
But using meld or diff, I can see so many changes that I would like to
open discussion on the impact of backporting changes to
releases/0.11.14.
meld meld trunk/ releases/opensc-0.11.14/
...
IM
