Peter. If you were a book editor waiting for a perfect book, you could
be waiting for ages and as a result would NOT edit ANY book. This is
what is happening to OpenSC, with dozens of patch waiting for the
perfect developer.
The perfect patch just does not exist. Quality is a continuous process
of
Jean-Michel Pouré - GOOZE wrote:
> ease the collaboration process quickly or the community will set-up
> its own tools.
Please stop blowing smoke. You want to fork so GO AND DO IT ALREADY!
You clearly have no desire to work together with all members of the
community. You've decided that only your
Dear Ludovic,
> That may be the best solution: to restart from a synchronised state.
> I hope Martin will have more free time in a few days to implement
> that.
As written several times before, we need more people with admin rights
on OpenSC projects. There is no reason to limit to two people: Lu
Le 4 avril 2012 09:49, Viktor Tarasov a écrit :
> On Tue, Apr 3, 2012 at 8:36 AM, Ludovic Rousseau
> wrote:
>>
>> Le 3 avril 2012 00:30, Viktor Tarasov a écrit :
>> > Le 02/04/2012 10:01, Ludovic Rousseau a écrit :
>> >> Le 2 avril 2012 09:56, Jean-Michel Pouré - GOOZE a
>> >> écrit :
>> I
On Tue, Apr 3, 2012 at 8:36 AM, Ludovic Rousseau wrote:
> Le 3 avril 2012 00:30, Viktor Tarasov a écrit :
> > Le 02/04/2012 10:01, Ludovic Rousseau a écrit :
> >> Le 2 avril 2012 09:56, Jean-Michel Pouré - GOOZE a
> écrit :
> I don't think there is.
> >>> Here is the address of the secure
Le 3 avril 2012 00:30, Viktor Tarasov a écrit :
> Le 02/04/2012 10:01, Ludovic Rousseau a écrit :
>> Le 2 avril 2012 09:56, Jean-Michel Pouré - GOOZE a écrit :
I don't think there is.
>>> Here is the address of the secure messaging branch:
>>> https://github.com/viktorTarasov/OpenSC-SM/tree/
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
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
> opens
Le 02/04/2012 10:01, Ludovic Rousseau a écrit :
> Le 2 avril 2012 09:56, Jean-Michel Pouré - GOOZE 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 includes
Le 2 avril 2012 12:12, Peter Stuge 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 gerrit/s
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 expecte
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:
Le 2 avril 2012 10:34, Jean-Michel Pouré - GOOZE 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 you need
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?
Kind regards,
--
Jean-Michel Pouré - Gooze - http://www.gooze.eu
Le 2 avril 2012 09:56, Jean-Michel Pouré - GOOZE 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 includes most fixes.
>
> Binaries are published in:
> http://w
> 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 Op
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
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 Jerr
Le 29 mars 2012 09:55, Viktor Tarasov a écrit :
> Hello,
>
> On Wed, Mar 28, 2012 at 11:05 PM, Ludovic Rousseau
> wrote:
>>
>> Gerrit has more than 200 patches still waiting the the backlog.
>> Many of them can't be merge since they do not 'fast-forward' and must
>> be rebased by hand.
>>
>> Sinc
Le 29 mars 2012 09:55, Viktor Tarasov a écrit :
> Hello,
>
> On Wed, Mar 28, 2012 at 11:05 PM, Ludovic Rousseau
> wrote:
>> I do not know if a creating a french OpenSC association to deal with
>> the project governance will help here. But people with some free time
>> can surely help move OpenSC
Hello,
On Wed, Mar 28, 2012 at 11:05 PM, Ludovic Rousseau <
ludovic.rouss...@gmail.com> wrote:
> Gerrit has more than 200 patches still waiting the the backlog.
> Many of them can't be merge since they do not 'fast-forward' and must
> be rebased by hand.
>
> Since the git commits were created wit
Ludovic Rousseau wrote:
> Gerrit has more than 200 patches still waiting the the backlog.
> Many of them can't be merge since they do not 'fast-forward' and must
> be rebased by hand.
>
> Since the git commits were created without a Change-Id: we have 3
> options (I think):
> 1. edit each commit m
Hello,
Gerrit has more than 200 patches still waiting the the backlog.
Many of them can't be merge since they do not 'fast-forward' and must
be rebased by hand.
Since the git commits were created without a Change-Id: we have 3
options (I think):
1. edit each commit message to add the missing Chan
23 matches
Mail list logo
