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
On 6/7/2010 9:55 AM, Harry Anuszewski wrote:
> Hello,
>
> It has been a while. You know project delays. But I am now back on track.
> The script worked great. I am looking into decoding that output of the
> image so that I may view it and possibly get the header information from it.
> I am just s
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
Hello,
It has been a while. You know project delays. But I am now back on track.
The script worked great. I am looking into decoding that output of the
image so that I may view it and possibly get the header information from it.
I am just seeing if anyone could point me in a starting direction.
T
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
