Agree, we can send pull request in the mail list (without github),  just simply give your git repository URL and the branch name. The maintainer can pull/merge/review it easily.


On Sun, Feb 23, 2014 at 8:02 PM, Marco Antoniotti <marcoxa@cs.nyu.edu> wrote:

On Feb 23, 2014, at 05:51 , Daniel Herring <dherring@tentpost.com> wrote:

> On Sat, 22 Feb 2014, Philipp Marek wrote:
>
>> I might change my/the main repository over to github, though - it's much easier to
>> accept pull requests there than to import patches from emails.
>> Or are there any better ideas?
>
> Hi Philip,
>
> Thanks for lending a hand.  Its nice seeing bugfixes get committed.
>
> Please don't switch to Github simply for pull requests.  Stability is
> important for a project like this, and Github has a tendency to encourage
> fragmentation...  It gets bothersome tracking repository moves.  If you do
> start accepting pull requests over there, I would ask that you keep the SF
> repository up to date as the "primary" master.
>
> Are these emailed patches using git format-commit and git-am?  If not,
> then maybe encouraging their use would help you.
>

I second that.  DO NOT CHANGE ANY INFRASTRUCTURE CHOICES.  Even if I don’t work on ECL, these kind of changes are always very very disruptive for any community.

I also agree on the “fragmentation tendency of github”.

Cheers

MA



------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
Ecls-list mailing list
Ecls-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecls-list



--
-- 

KDr2, http://kdr2.com