commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hank Grabowski <h...@applieddefense.com>
Subject Re: [math] GitHub vs ASF Repo
Date Tue, 14 Oct 2014 13:16:58 GMT
Should I try an experiment with that with those interpolator changes I put
the diff into JIRA for and remove that flle from the JIRA issue or is the
process of using that diff already underway so it would create more brain
daamge than it was worth?

On Tue, Oct 14, 2014 at 9:12 AM, luc <luc@spaceroots.org> wrote:

> Hi Hank,
>
> Le 2014-10-14 15:01, Gilles a écrit :
>
>> On Tue, 14 Oct 2014 08:36:07 -0400, Hank Grabowski wrote:
>>
>>> It seems that the GitHub repository is now staying in sync with the ASF
>>> repository.  Is the preferred workflow going to be (or already is)
>>> forking
>>> inside of GitHub and then doing pull requests or will the workflow be to
>>> work directly with ASF?  For someone like me with only read only access
>>> to
>>> the ASF it seems that the fork method is better than submitting diff
>>> files
>>> attached to JIRA incidents.
>>>
>>
>> [Non authoritative answer; I'm still far from up to speed with git...]
>>
>> I think that all three ways are fine; it's your choice.
>>
>
> Yes, you can do as you want.
> As [math] is expereimenting here, the processe is not fully defined.
>
> What *is* fully defined however is that the mailing list is the place of
> choice for discussing changes.
> Once discussion has settled, I think we can grab patches from almost
> anyware.
>
> best regards,
> Luc
>
>
>
>> Gilles
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message