> Hi Geoffroy, > > Either (shar/diff) is fine, but diffs can help with (inline) review, or > in the event further changes are needed. > > With svn diffs, you can also include changes such as adding the ports to > the relevant category/Makefile as well (which are needed for new ports), > save committer time, and gets you familiar with our side of the process. > Well, I'll try this way then :)
> The multiple ports question is less concrete, as its a balance between > overhead per PR (with perhaps a single committer), and isolated changes. > > If it were me, I'd create a single issue report, with one patch per > port, named perfectly (with descriptions) > > Mention in the submission which are dependencies of which and go from there. > > More important than submission formats however, are: > > - portlint output is clean (see ports-mgmt/portlint) Already portlint lover… > - Build/Package QA and tested with poudriere or redports > …and in process of configuring poudriere for QA :) > Jump on #freebsd-ports (freenode) or #bsdports (efnet) if you have any > questions, and have fun! > Thank you ! -- *geoffroy desvernay* C.R.I - Administration systèmes et réseaux Ecole Centrale de Marseille
signature.asc
Description: OpenPGP digital signature