Okay not a problem. Actually the number of files are fairly small for the first "big" port patch about 10 or so I think and its basically impossible to get a compile without these base files.
I'll put together a patch in the next few days and submit it. After that much smaller patches are resonable. On 4/6/06, Maciej Stachowiak <[EMAIL PROTECTED]> wrote: > > On Apr 6, 2006, at 12:01 PM, Mike Emmel wrote: > > > I'm getting close to something thats worth putting up. > > > > If there is any paperwork for svn access I should probably go ahead > > and start it. > > As Darin mentioned, the usual process, including for ports, is to > start submitting patches. Ideally patches should come in increments > that can reasonably be reviewed, not just "here's a whole new port". > We often grant direct commit access to people who submit a sufficient > number and quality of patches and show themselves to be responsible, > but it is not step 1. > > One of the most important first steps, once you have at least some > things compiling, would be to set up a build system for your port. > That way others can try it out and we can eventually set up a buildbot. > > Regards, > Maciej > > P.S. We do have reviewers with Gtk experience and definitely with > Cairo experience so there shouldn't be a problem with understanding > the patches. > _______________________________________________ webkit-dev mailing list [email protected] http://www.opendarwin.org/mailman/listinfo/webkit-dev
