I have sent a pull request to github, wich includes 3 different commits but all listed under the same pull request. (I would have suspected it let be do 3 pull requests.)
https://github.com/dengert/OpenSC/commit/1542022a6aefb86de95c734bb3923f2b3b59490e Needed to get code to compile. https://github.com/dengert/OpenSC/commit/d36b8fc45e8e77cd620976cb5c21c08baecd0480 Updates some comments and removes the "PIN Always" from the PIV 9D key. https://github.com/dengert/OpenSC/commit/8052e2f940810f3010542933619d18b98488e84a Implements a solution to the problem described in my message "[opensc-devel] OpenSC, CK_ALWAYS_AUTHENTICATE and Thunderbird" from 8/6/2012 I would like to see these in 0.13.0 if possible as there are users with these problems. On 8/6/2012 9:34 AM, Douglas E. Engert wrote: > I am going to send shortly, under a different subject, a problem dealing with > user_consent, > CK_ALWAYS_AUTHENTICATE, OpenSC and Thunderbird. I would like to see it > addressed in > the next release. > > > On 8/5/2012 12:48 PM, Viktor Tarasov wrote: >> Hello, >> >> Le 22/07/2012 17:44, Viktor Tarasov a écrit : >>> I would like to start preparation of the new release based on the 'staging' >>> branch of GitHub OpenSC . >>> Your suggestions proposals are heartily welcome. >>> >>> As far as I see all 'essential' proposals, >>> that have be committed into the 'staging' branch of OpenSC git repository >>> hosted in opensc-project.org (git://www.opensc-project.org/OpenSC.git), >>> are present in github OpenSC. >>> >>> Unfortunately there is no access to the code review service (gerrit) of >>> opensc-project.org and it's not currently possible to pick-up the >>> 'interesting' requests. >>> So, if anybody interested to see these proposals in the next release, >>> please, do pull request to 'staging' branch of GitHub OpenSC >>> (git://github.com/OpenSC/OpenSC.git) . >> >> If anyone has more or less significant proposals, especially the ones that >> touch the common framework, >> please, create the pull requests for github OpenSC.git/staging until the >> next weekend . >> Don't worry if you will not arrive until this term -- I hope to make >> automatic the essential part of release process and so, >> to make releases more frequents. >> >> The next weekend I hope to start the advanced non-regression tests of the >> current 'staging' and to tag the candidate for release. >> >> Look also if something essential is missing in the current 'NEWS' of >> 'staging'. >> Sorry, 'NEWS' do not reflects in details all the contributions that have >> been made during the last year -- they are too numerous. >> >> 'Codereview' service of opensc-project.org is still not accessible and so >> there is no possibility to pick-up >> the 'useful' proposals that have been made there. >> >> Kind regards, >> Viktor. >> _______________________________________________ >> opensc-devel mailing list >> opensc-devel@lists.opensc-project.org >> http://www.opensc-project.org/mailman/listinfo/opensc-devel >> >> > -- Douglas E. Engert <deeng...@anl.gov> Argonne National Laboratory 9700 South Cass Avenue Argonne, Illinois 60439 (630) 252-5444 _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
