[PATCH 1 of 2 V2] wlock: only issue devel warning when actually acquiring the lock

Martin von Zweigbergk martinvonz at google.com
Mon Apr 13 22:57:45 CDT 2015


On Mon, Apr 13, 2015 at 8:46 PM Ryan McElroy <rm at fb.com> wrote:
>
> A meta-point/question: I often find it would be useful to see how a test
> behaved *before* a fix. What does the community think about a patch that
> introduces a test that shows a failure, followed by a patch that fixes
> the code and shows how the behavior is now fixed and better than before?
> I might start doing this in my patches...
>

I brought this up here:
http://thread.gmane.org/gmane.comp.version-control.mercurial.devel/75747/focus=75752

I haven't taken the time to add that syntax to the test runner yet.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20150414/97326623/attachment.html>


More information about the Mercurial-devel mailing list