GitHub is great about allowing forks of projects. I say create a fork, then, when you're all ready to "submit" a patch, issue a pull request.
On Nov 13, 1:54 pm, "Yariv Sadan" <[email protected]> wrote: > I think the best way is through the mailing list. I generally accept > any useful patch. > > Yariv > > On Thu, Nov 13, 2008 at 10:49 AM, Michael Mullis > > <[email protected]> wrote: > > > With the move to git, what's going to be the best way to submit issues > > and track patches? > > The issues reported onhttp://code.google.com/p/erlyweb/ don't seem > > to be moving > > so I'm wondering what the future is for erlyweb. > > > Other thoughts? > > /michael. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "erlyweb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/erlyweb?hl=en -~----------~----~----~----~------~----~------~--~---
