Le 07/10/2014 20:15, Luc Maisonobe a écrit :
> Le 07/10/2014 17:34, Ole Ersoy a écrit :
>> Do I need to wait for the repositories to become synchronized before
>> doing another pull request? It's only a tiny documentation change.
>
> No, you can do it with the current repository, we'll refactor t
Le 07/10/2014 17:34, Ole Ersoy a écrit :
> Do I need to wait for the repositories to become synchronized before
> doing another pull request? It's only a tiny documentation change.
No, you can do it with the current repository, we'll refactor the patch
as needed.
best regards
Luc
>
> Thanks,
>
Do I need to wait for the repositories to become synchronized before doing
another pull request? It's only a tiny documentation change.
Thanks,
- Ole
On 10/03/2014 06:46 AM, Luc Maisonobe wrote:
Le 02/10/2014 17:51, Ole Ersoy a écrit :
Hello Luc, Gilles, and Benedikt,
I'm here :). From my
Le 03/10/2014 16:46, Ole Ersoy a écrit :
> Ooops - Sorry Luc, slight mental glitch there - I wrote Luke instead of
> Luc :).
Use git push --force, Luc :)
Emmanuel Bourg
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.o
Ooops - Sorry Luc, slight mental glitch there - I wrote Luke instead of Luc :).
Cheers,
- Ole
On 10/03/2014 06:46 AM, Luc Maisonobe wrote:
Le 02/10/2014 17:51, Ole Ersoy a écrit :
Hello Luc, Gilles, and Benedikt,
I'm here :). From my limited github experience, I do think most
contributors d
Gilles, Luke, Phil,
I respect what you are saying. All I'm saying is that I think using Git to
it's full potential will be more attractive and less confusing to future
contributors. I'm really not trying to lobby strongly for this though. I just
shared my thoughts on it in case the move to
The reason there is a difference is that the GitHub mirror was based on
an early git mirror when our main repository was subversion. We have
switched to Git only a few weeks ago, and the official original git
repository has been recreated from the subversion history, not from the
other git mirror.
Le 02/10/2014 17:51, Ole Ersoy a écrit :
> Hello Luc, Gilles, and Benedikt,
>
> I'm here :). From my limited github experience, I do think most
> contributors do their communication directly through github. I've seen
> a lot of projects use issues for discussion. I personally like this,
> becau
Hi all,
Le 03/10/2014 12:17, Gilles a écrit :
> Hi.
>
> On Thu, 02 Oct 2014 15:35:53 -0500, Ole Ersoy wrote:
>> On 10/02/2014 02:18 PM, Phil Steitz wrote:
>>> On 10/2/14 11:33 AM, Ole Ersoy wrote:
Hi,
On 10/02/2014 11:34 AM, Gilles wrote:
> Hello.
>
> On Thu, 02 Oct 201
Hi.
On Thu, 02 Oct 2014 15:35:53 -0500, Ole Ersoy wrote:
On 10/02/2014 02:18 PM, Phil Steitz wrote:
On 10/2/14 11:33 AM, Ole Ersoy wrote:
Hi,
On 10/02/2014 11:34 AM, Gilles wrote:
Hello.
On Thu, 02 Oct 2014 10:51:53 -0500, Ole Ersoy wrote:
Hello Luc, Gilles, and Benedikt,
I'm here :). Fr
On 10/02/2014 02:18 PM, Phil Steitz wrote:
On 10/2/14 11:33 AM, Ole Ersoy wrote:
Hi,
On 10/02/2014 11:34 AM, Gilles wrote:
Hello.
On Thu, 02 Oct 2014 10:51:53 -0500, Ole Ersoy wrote:
Hello Luc, Gilles, and Benedikt,
I'm here :). From my limited github experience, I do think most
contribu
On 10/2/14 11:33 AM, Ole Ersoy wrote:
> Hi,
>
> On 10/02/2014 11:34 AM, Gilles wrote:
>> Hello.
>>
>> On Thu, 02 Oct 2014 10:51:53 -0500, Ole Ersoy wrote:
>>> Hello Luc, Gilles, and Benedikt,
>>>
>>> I'm here :). From my limited github experience, I do think most
>>> contributors do their communic
Hi,
On 10/02/2014 11:34 AM, Gilles wrote:
Hello.
On Thu, 02 Oct 2014 10:51:53 -0500, Ole Ersoy wrote:
Hello Luc, Gilles, and Benedikt,
I'm here :). From my limited github experience, I do think most
contributors do their communication directly through github.
"Commons" contributors?
I sh
Hello.
On Thu, 02 Oct 2014 10:51:53 -0500, Ole Ersoy wrote:
Hello Luc, Gilles, and Benedikt,
I'm here :). From my limited github experience, I do think most
contributors do their communication directly through github.
"Commons" contributors?
I've
seen a lot of projects use issues for discu
Hello Luc, Gilles, and Benedikt,
I'm here :). From my limited github experience, I do think most contributors
do their communication directly through github. I've seen a lot of projects
use issues for discussion. I personally like this, because it makes it easy to
get up to speed on design
On Thu, 2 Oct 2014 11:48:19 +0200, Benedikt Ritter wrote:
Hi Luc,
this emails are outgenerated when a PR is created at github, so I
wouldn't
expect the contributor to be subscribed to the list. It's probably
better
to comment on the PR at github.
Sorry to intervene; but why is it better to
Hi Luc,
this emails are outgenerated when a PR is created at github, so I wouldn't
expect the contributor to be subscribed to the list. It's probably better
to comment on the PR at github.
Benedikt
2014-09-30 9:55 GMT+02:00 luc :
> Hi Ole,
>
> Le 2014-09-30 02:09, oleersoy a écrit :
>
>> GitHub
Hi Ole,
Le 2014-09-30 02:09, oleersoy a écrit :
GitHub user oleersoy opened a pull request:
https://github.com/apache/commons-math/pull/4
Updated the example documentation for the GaussianCurveFitte
You can merge this pull request into a Git repository by running:
$ git pull ht
GitHub user oleersoy opened a pull request:
https://github.com/apache/commons-math/pull/4
Updated the example documentation for the GaussianCurveFitte
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/oleersoy/commons-math trunk
A
19 matches
Mail list logo
