[[ This message was both posted and mailed: see
the "To," "Cc," and "Newsgroups" headers for details. ]]
In article <20100329135115.GG7...@fsck.bestpractical.com>, Jesse
Vincent <je
...@fsck.com> wrote:
> From the docs in perlfaq.pod, I presume it's right to forward this to
> perlfaq-workers and not to patch the version in blead directly. Please
> correct me if I'm wrong on that.
It's fine to forward it to perlfaq-workers, but none of the ways that I
deal with this mailing list (which is not in the big blackhole of
nevergettingdonedness called email) preserves the patch attachements.
So, I don't have the patch. Can someone put it in the body?
However, this dual life stuff is really a pain in the ass now. It was
fine in Subversion when the dual life pain was less than the Perforce
pain, but now the dual life pain is greater than the git pain. Patches
in anything other than a github fork just seem archaic now. :)
