An additional bundle to fix the test for issue1923.
Note: the fix for issue2603 means that clone --lazy is no longer lazy on
patches after the latest clean tag. I think there is no way to avoid that.
1 patch for repository http://darcs.net/screened:
patch 94ac9a2ad4d8ce4f510d4f34feb98aa00dc9f6bb
Author: Ben Franksen <ben.franksen@online.de>
Date: Thu Nov 15 17:34:44 CET 2018
* fix test for issue1923 after fix for issue2603 broke it
The fix for issue2603 adds a call to patchsetConflictResolutions on the
newly cloned repo. This procedure must look at the content of every patch in
the head inventory i.e. all patches after the latest clean tag. This
effectively forces these patches, so they are no longer lazy. So the bogus
sources that the test fakes for the new repo aren't even looked at. The fix
is simple: just record a tag after the single patch.
Attachments
|