Re: [Rails-devel] Creating patches/commits

[brett l. <wak...@gm...>]

Anyone can send patches to the mailing list.  If they look good, we'll
apply them to the cvs tree.

Frequent patch submission will earn you access to commit directly, if
you want it.

---Brett.



On Tue, Jan 5, 2010 at 9:12 AM, Phil Davies <de...@gm...> wrote:
> How do you handle changes or submissions to the codebase?  I've
> noticed that the game notes for 18EU are incorrect since they say that
> the mountain tile upgrade costs are not implemented yet, when as far
> as I can tell (through looking at code and by playing to that stage)
> they are working fine.
>
> Seems pointless creating a bug for something so quick to fix, I'll go
> and poke it myself but didn't really know how you handle code control.
>  Just create a patch and send it to someone for approval or request
> access for direct commit (seems dangerous to me!)
>
> I'm keen to help out in whatever small way I can :)
>
> Phil Davies
>
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel
>