[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Octave Forge] Octave 4.0 call for packages
From: |
Carnë Draug |
Subject: |
Re: [Octave Forge] Octave 4.0 call for packages |
Date: |
Tue, 14 Apr 2015 11:28:02 +0100 |
On 14 April 2015 at 11:20, Carnë Draug <address@hidden> wrote:
> On 14 April 2015 at 11:01, c. <address@hidden> wrote:
>>
>> On 14 Apr 2015, at 11:47, Carnë Draug <address@hidden> wrote:
>>
>>> Everyone. Every OF developer has push access to all OF repositories.
>> are sebastian and jacopo registered as OF developers? how can I check?
>
> No. Unless they use some alias, I don't see their names in the list of
> developers.
> But Jacopo was a SoCiS student, he shouldn't have received access, it should
> had been his mentor that reviewed and pull his changes. I don't know about
> Sebastian but I can't find anything on the mailing list archive either.
>
This also applies to Roberto's changes which appear to have never been
pushed to OF. The position is the same as I mentioned here:
http://octave.1599824.n4.nabble.com/Odeset-Odeget-tp4656954p4657216.html
On Sep 11, 2013, Carnë Draug wrote:
> The idea is that package maintainers get commit access to the
> repository since contributors can now ask for pull requests. So what
> would happen is you make your commits locally, push to some repo
> anywhere (Jordi will host one for you if you want, otherwise you could
> use something such as bitbucket) and ask your mentor to pull your
> changes. He would then comment on your changes and pull them as he
> sees fit.
Also, regarding this two posts from 4 months ago:
http://octave.1599824.n4.nabble.com/odepkg-odeset-profile-tests-tp4667635p4667682.html
http://octave.1599824.n4.nabble.com/odepkg-odeset-profile-tests-tp4667635p4667637.html
You don't need to ask for a pull request in bitbucket. You can pull the
changes you reviewed into your local clone, and then push them to OF.
They would then update their own clone (and the one in their bitbucket
account), with your merge.
Carnë
- Re: [Octave Forge] Octave 4.0 call for packages, (continued)
- Re: [Octave Forge] Octave 4.0 call for packages, Carnë Draug, 2015/04/13
- Re: [Octave Forge] Octave 4.0 call for packages, c., 2015/04/13
- Re: [Octave Forge] Octave 4.0 call for packages, Tatsuro MATSUOKA, 2015/04/13
- Re: [Octave Forge] Octave 4.0 call for packages, c., 2015/04/14
- Re: [Octave Forge] Octave 4.0 call for packages, Tatsuro MATSUOKA, 2015/04/14
- Re: [Octave Forge] Octave 4.0 call for packages, Carnë Draug, 2015/04/14
- Re: [Octave Forge] Octave 4.0 call for packages, c., 2015/04/14
- Re: [Octave Forge] Octave 4.0 call for packages, Carnë Draug, 2015/04/14
- Re: [Octave Forge] Octave 4.0 call for packages,
Carnë Draug <=
- Re: [Octave Forge] Octave 4.0 call for packages, c., 2015/04/14
- Re: [Octave Forge] Octave 4.0 call for packages, Carnë Draug, 2015/04/14
- Re: [Octave Forge] Octave 4.0 call for packages, c., 2015/04/14
- Re: [Octave Forge] Octave 4.0 call for packages, Sebastian Schöps, 2015/04/14
- Re: [Octave Forge] Octave 4.0 call for packages, c., 2015/04/16
- Re: [Octave Forge] Octave 4.0 call for packages, Sebastian Schoeps, 2015/04/16
- Re: [Octave Forge] Octave 4.0 call for packages, c., 2015/04/16
- Re: [Octave Forge] Octave 4.0 call for packages, Carnë Draug, 2015/04/16
- Re: [Octave Forge] Octave 4.0 call for packages, Jacopo Corno, 2015/04/16
- Re: [Octave Forge] Octave 4.0 call for packages, Carnë Draug, 2015/04/16