Re: [pok-devel] ARINC-653 intrapartition communication compatibility

You can also discuss the modification beforehand on this mailing list and explain the changes that are supposed to appear in the generated code. Then, we can see if this is difficult to adapt and if not, we just adapt our code generator and you can just push your changes. Does that sound reasonable?

On Mon, Mar 3, 2014 at 6:31 AM, Etienne Borde <etienne.borde@xxxxxxxxxxxxxxxxxxxx> wrote:

Hi Maximilien,

a convenient way to do this is to make a fork from the git repository (their is just on button to click on in order to do this in github).
Then you comit/push in your forked version.

You give us a link to this fork, and if the modifications are accepted then you ask for a pull request (on button to click on in order to do this in github).

I guess this is the proper way to proceed, I am of course open for other suggestions.

Etienne.

----- Mail original -----

De: "Maxim Malkov" <malkov@xxxxxxxxx>
À: pok-devel@xxxxxxxxxxxxxxxxxxx
Envoyé: Lundi 3 Mars 2014 11:15:45

Objet: Re: [pok-devel] ARINC-653 intrapartition communication compatibility

On 22.02.2014 16:17, Julien Delange wrote:
> Well, I guess this would be the right thing to do! I used SVN at that
> time because git did not exists ... but I figured that things change
> and it will be time to switch to a new control system version! Also,
> this would then solve Etienne issue, his student could have its own
> version!
>
> Let me work on this, I will then migrate the repository on github
> within a few days ...
>
> Thanks !
I guess I'll just rebase my work on top of your new repository head,
publish it somewhere and post a link here. And then you'll decide
whether to pull from it or not.

--
Maxim Malkov
Software Engineering Department, ISPRAS