Patch frustration

Adrian Buehlmann adrian at cadifra.com
Wed Jun 6 19:19:38 CDT 2012


The current system of contributing and reviewing patches is an absolute
pain.

Especially for people like me who contribute bursts of lot of small,
boring, low-risk patches.

Having to wait a week for a small tiny low-risk patch or seeing it
getting off the table without a resolution can be quite nerve-racking.
The nerve-rackingness increases with the number of outstanding patches
and with the level of scrutinity applied by the reviewer. Which is
sometimes pretty hard to understand ("why is it needed to nitpick about
that detail?").

So, If I have come across dense to reviewers, and especially Mads, I
apologize. It wasn't intentional.

And if people have a problem with me or my contributions, then please
say so. Perhaps off-line.

Thank you.

P.S.
On the TortoiseHg project, when it was more active in the past, patches
were pushed at a pretty high cadence (low latency means something). This
was pretty important and resulted in a very productive environment. Of
course this can't be compared to Mercurial, as Mercurial patches are
often a lot more difficult and have a higher risk. But perhaps there
could be areas identified where a bit less scrutinity would be
acceptable. A little bit more of moving fast and possibly breaking things.


More information about the Mercurial-devel mailing list