Whenever you send patches or new ports to the list, remember there's
some asynchronous behavior involved.
There's been some recent confusion as to which version of a patch someone
was referring to, because it was an external link, and the external link
got changed to something else.
That's a common rookie mistake: as soon as you publish/send a patch link
to someone, consider that link "eternal". If you change the patch later,
it's totally trivial to give it a version number, and *make sure to provide
a different link*.
Otherwise, it's really easy to lose track and attribution. And such mix-ups
tend to lead to the wrong code being committed ('but he said it was okay....
nah, I never saw that version of the patch....'), which leads to further
time lost to figure out the fuck-up...
Also, your work may be more easily/quickly reviewed if it's included
*directly* in your email.
For instance, very often, I don't have any modern browser available while
I'm testing dpb.
even if I have a browser, clicking on a link involves a second step.
heck, apart from ports, we routinely remove attachments to all the lists.
People with commit access are chronically overworked. every small thing you
can do to make things easier is generally appreciated, thank you.
