Le dimanche 01 avril 2012 à 23:21 +0200, Ludovic Rousseau a écrit :
No one volunteered to help. As I wrote in my initial email, I now do
plan for option 3.
Ludovic, please listen to us.
There is also the option 4, proposed by Viktor:
Anyway, now that you plan to reject ALL patches from
Jean-Michel Pouré - GOOZE wrote:
community, is there a way to agree to switch the 'public
staging' to 'SM' and use it as a principal base for releases?
I don't think there is.
//Peter
pgpmvOdeyPmxt.pgp
Description: PGP signature
___
opensc-devel
I don't think there is.
Here is the address of the secure messaging branch:
https://github.com/viktorTarasov/OpenSC-SM/tree/secure-messaging
We are using it, as it includes most fixes.
Binaries are published in:
http://www.opensc-project.org/downloads/nightly/sm/
Why not use Opensc-SM for
Le 2 avril 2012 10:34, Jean-Michel Pouré - GOOZE jmpo...@gooze.eu a écrit :
Dear all,
1. rebase the SM branch over the OpenSC version in gerrit/staging
You do not need extra power for that. It is just normal developer
work.
Okay. So all we need is a diff between SM and staging?
No. What
Le lundi 02 avril 2012 à 10:46 +0200, Ludovic Rousseau a écrit :
No. What you need is to extract all the SM patches and apply them on
the gerrit/staging branch.
Of course some conflicts are expected and need to be fixed.
What I would do (but I am not a git expert)
on the SM branch use: git
Ludovic Rousseau wrote:
1. rebase the SM branch over the OpenSC version in gerrit/staging
Okay. So all we need is a diff between SM and staging?
No. What you need is to extract all the SM patches and apply them
on the gerrit/staging branch.
Of course some conflicts are expected and need
Le 2 avril 2012 12:12, Peter Stuge pe...@stuge.se a écrit :
Ludovic Rousseau wrote:
1. rebase the SM branch over the OpenSC version in gerrit/staging
Okay. So all we need is a diff between SM and staging?
No. What you need is to extract all the SM patches and apply them
on the
INPUT:
http://www.opensc-project.org/opensc/wiki/UsingOpensc
OUTPUT:
Traceback (most recent call last):
File build/bdist.linux-x86_64/egg/trac/web/api.py, line 440, in send_error
data, 'text/html')
File build/bdist.linux-x86_64/egg/trac/web/chrome.py, line 827, in
render_template
Le 2 avril 2012 13:30, helpcrypto helpcrypto helpcry...@gmail.com a écrit :
INPUT:
http://www.opensc-project.org/opensc/wiki/UsingOpensc
Now fixed.
Thanks
--
Dr. Ludovic Rousseau
___
opensc-devel mailing list
Le 02/04/2012 10:01, Ludovic Rousseau a écrit :
Le 2 avril 2012 09:56, Jean-Michel Pouré - GOOZE jmpo...@gooze.eu a écrit :
I don't think there is.
Here is the address of the secure messaging branch:
https://github.com/viktorTarasov/OpenSC-SM/tree/secure-messaging
We are using it, as it
Viktor Tarasov wrote:
How the 'staging', that you are working on, is related to the
'staging' branch of the OpenSC.git from github ?
Looking onto the git workflow
(https://www.opensc-project.org/opensc/wiki/DevelopmentPolicy)
I do not quite understand the place of 'staging' on the
Ludovic Rousseau wrote:
on the SM branch use: git format-patch origin to get the changes
in individual patch files.
on the gerrit/staging use: git am my_patch for all the previously
generated patches.
I would avoid doing this manually. git rebase really is the way to go.
I am still
12 matches
Mail list logo
