Patch 1479 resolve issue2138: report conflicting files in whatsne...

Title resolve issue2138: report conflicting files in whatsne...
Superseder Nosy List gh
Related Issues
Status accepted Assigned To

Created on 2016-04-08.21:52:09 by gh, last changed 2016-04-19.15:15:02 by gh.

File name Status Uploaded Type Edit Remove
patch-preview.txt gh, 2016-04-08.21:52:08 text/x-darcs-patch
resolve-issue2138_-report-conflicting-files-in-whatsnew-_s.dpatch gh, 2016-04-08.21:52:08 application/x-darcs-patch
unnamed gh, 2016-04-08.21:52:08 text/plain
See mailing list archives for discussion on individual patches.
msg19148 (view) Author: gh Date: 2016-04-08.21:52:08
See IRC discussion at

http://irclog.perlgeek.de/darcs/2016-04-08#i_12308345 .

1 patch for repository http://darcs.net:

patch 585efe389622886c8de70c26100676ed336e2eb7
Author: Guillaume Hoffmann <guillaumh@gmail.com>
Date:   Fri Apr  8 19:08:34 ART 2016
  * resolve issue2138: report conflicting files in whatsnew -s
msg19161 (view) Author: gh Date: 2016-04-11.18:36:04
I have had sometimes bad run times for "whatsnew -s" on darcs.net's

Clearly, finding out which files are conflicting can be costlier than
just running a diff of the working copy. For a start, we need to read
patches. This means "whatsnew -s" on lazy repositories will imply
downloading patches.

What do we know about the function patchsetConflictResolutions, and can
we improve its performance?
msg19178 (view) Author: gh Date: 2016-04-19.15:15:02
I'm self-accepting the patch. It implements an important feature, and we
should try to optimize it later.
Date User Action Args
2016-04-08 21:52:09ghcreate
2016-04-08 21:54:54ghsetstatus: needs-screening -> needs-review
2016-04-11 18:36:04ghsetmessages: + msg19161
2016-04-19 15:15:02ghsetstatus: needs-review -> accepted
messages: + msg19178