Hello.
On Mon, 11 Apr 2016 08:04:54 -0400, Rob Tompkins wrote:
All,
I was thinking about this some over the weekend. How many of the
contributors (those without commit access to the apache repository),
do you think, will be accessing and submitting code via GitHub pull
request? I ask because Gi
All,
I was thinking about this some over the weekend. How many of the contributors
(those without commit access to the apache repository), do you think, will be
accessing and submitting code via GitHub pull request? I ask because GitHub
offers a template mechanism for pull requests.
Generally,
On Fri, 08 Apr 2016 16:18:25 +0200, Gilles wrote:
Hello.
Struggling with how to share non-committer contributions:
https://issues.apache.org/jira/browse/MATH-1290
At some point, we should have a paragraph in
doc/development/development.howto.txt
that would explain which steps the contributo
Hi.
I'm not fluent enough in "git" and never used "Github", so most
of what you write below is not at all clear to me.
Also, I'm not sure that we talk from the same basis.
Just to be sure: Commons Math is not hosted at "Github"; the "Github"
site is merely a "one-way" mirror.
Committers must "pu
Hey Gilles,
Having been thinking about these sorts of ideas considerably in my day job, it
might be worth considering adding some status checks for formatting. These
aren’t too difficult to implement, but do require some mechanics.
Its mainly having github POST to some configured url, and havi
Hello.
Struggling with how to share non-committer contributions:
https://issues.apache.org/jira/browse/MATH-1290
At some point, we should have a paragraph in
doc/development/development.howto.txt
that would explain which steps the contributor and committer must
follow (i.e. one, simple, fool
On Wed, Jan 6, 2016 at 6:48 PM, Gilles wrote:
> On Wed, 6 Jan 2016 18:42:06 +0100, Luc Maisonobe wrote:
>
>> Le 06/01/2016 15:56, Gilles a écrit :
>>
>>> Hi.
>>>
>>> I've reread this article (which IIRC was advertised on this list some
>>> time ago):
>>> http://nvie.com/posts/a-successful-git-b
On Thu, 7 Jan 2016 21:29:48 +0100, Luc Maisonobe wrote:
Hi Sebb,
Le 07/01/2016 04:21, sebb a écrit :
On 7 January 2016 at 01:48, Gilles
wrote:
On Wed, 6 Jan 2016 18:42:06 +0100, Luc Maisonobe wrote:
Le 06/01/2016 15:56, Gilles a écrit :
Hi.
I've reread this article (which IIRC was advert
Hi Sebb,
Le 07/01/2016 04:21, sebb a écrit :
> On 7 January 2016 at 01:48, Gilles wrote:
>> On Wed, 6 Jan 2016 18:42:06 +0100, Luc Maisonobe wrote:
>>>
>>> Le 06/01/2016 15:56, Gilles a écrit :
Hi.
I've reread this article (which IIRC was advertised on this list some
time
On 7 January 2016 at 01:48, Gilles wrote:
> On Wed, 6 Jan 2016 18:42:06 +0100, Luc Maisonobe wrote:
>>
>> Le 06/01/2016 15:56, Gilles a écrit :
>>>
>>> Hi.
>>>
>>> I've reread this article (which IIRC was advertised on this list some
>>> time ago):
>>> http://nvie.com/posts/a-successful-git-bran
On Wed, 6 Jan 2016 18:42:06 +0100, Luc Maisonobe wrote:
Le 06/01/2016 15:56, Gilles a écrit :
Hi.
I've reread this article (which IIRC was advertised on this list
some
time ago):
http://nvie.com/posts/a-successful-git-branching-model/
It is quite clear and I think that it would easy to get
Le 06/01/2016 15:56, Gilles a écrit :
> Hi.
>
> I've reread this article (which IIRC was advertised on this list some
> time ago):
> http://nvie.com/posts/a-successful-git-branching-model/
>
> It is quite clear and I think that it would easy to get used to.
Yes, it is quite a good model.
> Un
Hi.
I've reread this article (which IIRC was advertised on this list some
time ago):
http://nvie.com/posts/a-successful-git-branching-model/
It is quite clear and I think that it would easy to get used to.
Unless there are shortcomings that would prevent its use with the CM
repository, I propo
13 matches
Mail list logo
