- page 1 of 376
- next ->
It should have been removed by this patch from 2009: "Resolve issue1366: remove unreachable code for direct ncurses use".
|gh||Tue Mar 24 18:48:40 UTC 2015|
|gh||Fri Mar 20 20:38:32 UTC 2015|
|gh||Fri Mar 20 20:27:02 UTC 2015|
|gh||Tue Mar 17 20:16:49 UTC 2015|
|gh||Tue Mar 17 19:55:10 UTC 2015|
|bfr||Tue Mar 10 20:03:32 UTC 2015|
|bfr||Tue Mar 10 11:58:16 UTC 2015|
It is commonly agreed upon that fail is an ugly wart in the Monad class and should not be used for serious programs. Its only sensible justification is to support de-sugaring of do blocks with failing pattern matches.
|bfr||Tue Mar 10 11:54:23 UTC 2015|
This brings it in line with how messages in Darcs are formatted elsewhere.
|bfr||Sat Mar 7 12:25:46 UTC 2015|
The IO that was in Darcs.UI.Defaults has been moved to the caller (Darcs.UI.RunCommand.runCommand). This allows us to fix a regression: relative paths given as option arguments in defaults files were not resolved with respect to the same working directory as when giving the option on the command line. The ordering constraints of commandPrereq vs. getGlobal/getPreflist are now concentrated in one place and documented.
Some changes related to errors and how to report them are also included in this patch since it would have been difficult to record them separately:
|bfr||Sun Feb 22 21:14:01 UTC 2015|
|gh||Sun Mar 8 20:13:53 UTC 2015|
|gh||Sun Mar 8 20:07:08 UTC 2015|
ename --patch-index to --with-patch-index to avoid conflict with existing --patch flag used with log and annotate
|gh||Sun Mar 8 19:50:19 UTC 2015|
|ganesh||Fri Mar 6 18:40:37 UTC 2015|
I've checked that new lower bounds (on binary, dataenc) work.
|ganesh||Thu Mar 5 06:45:27 UTC 2015|
|ganesh||Wed Mar 4 22:55:58 UTC 2015|
This fixes the build with mtl<2.2.1
|ganesh||Wed Mar 4 22:41:39 UTC 2015|
|ganesh||Tue Mar 3 07:56:53 UTC 2015|
|ganesh||Tue Mar 3 07:52:39 UTC 2015|
|ganesh||Wed Mar 4 06:29:06 UTC 2015|
|ganesh||Wed Mar 4 06:10:30 UTC 2015|
The two have different 'fail' implementations, but as far as I can see we don't have any explicit calls to that or any inexhaustive pattern matches in the relevant code.
|ganesh||Tue Mar 3 19:06:41 UTC 2015|
The previous code gave a false sense of security in its use of witnesses on the Repository type, because those can be implicitly mutated by operations on the repository but the Repository value with its old witnesses is still available for use.
The bug was that tentativelyReplacePatches should be passed the replacement patches, as it just adds them to the repository at the end after commuting out the previous versions. So when doing pull/apply --reorder, we need to pass in the local patches merged with the remote patches, rather than in their original form.
I reworked the code so that the witnesses are correct, which provokes a type error, and fixed the error by changing merge2FL to return both the merged remote patches and the merged local patches so the latter can be passed in to tentativelyReplacePatches.
|ganesh||Mon Mar 2 19:46:31 UTC 2015|
|ganesh||Mon Mar 2 20:04:39 UTC 2015|
|gh||Sat Feb 28 15:08:11 UTC 2015|
|gh||Sat Feb 28 15:07:50 UTC 2015|
|gh||Thu Feb 26 17:52:40 UTC 2015|
|gh||Thu Feb 26 17:50:31 UTC 2015|
|gh||Wed Feb 25 14:39:30 UTC 2015|
|gh||Fri Feb 27 17:29:04 UTC 2015|
- page 1 of 376
- next ->