On May 24, 2012, at 2:50 PM, Bjarne D Mathiesen wrote: > Bradley Giesbrecht wrote: >> >> Working in a svn tree is definitely the easiest way for you to collaborate >> with your fellow MacPorts contributers. >> >> If you were to run your script in a svn checkout of trunk/dports you would >> be able to provide the desired diff with "cd dports && svn diff > >> patch-perl5.16.diff". >> >> If you add the file:///trunk/dports tree to sources.conf you can hack and >> build to suit your own needs and "port sync" or "cd dports && svn up" will >> pull in changes leaving you to decide how to handle conflicts. > > OK ... I'll give it a try :-) > I haven't got that much experience with svn, git, hg > beyound the basics. > > Actually, what the two of us did with your hg is the most advanced I've > ever worked with version control !!! :-O
You will pick this up in no time :) > Now, when I've got that file, how / where do you want it ??? Create a MacPorts trac ticket with a nice subject and attach your file to the ticket. I'll watch for the ticket. You can add me "[email protected]" to the tickets cc field if you like. Regards, Bradley Giesbrecht (pixilla)
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
