- page 1 of 416
- next ->
C:is interpreted by tar as a network path, so we have to pipe it input instead.
|ganesh||Sat Nov 17 10:52:43 UTC 2018|
This test is intended to check behaviour on case-insensitive filesystems, but could never work in practice. It passed by accident for a while on Windows because it seems && doesn't interact properly with set -e.
Possibly this test should just be deleted, it's not clear what value it could ever have.
|ganesh||Fri Nov 16 15:43:19 UTC 2018|
This implementation does not use our self-written download manager in Darcs.Util.Download, which is needed only to interact with libcurl. Instead, speculating on a remote file is done simply by running the action in a background thread (using async) and relying on the connection manager that is supplied with http-conduit. This works pretty well and gives us the full functionality (including HTTPS) in a portable manner, so I switched the default for the curl flag in darcs.cabal to False.
|bf||Tue Sep 25 17:03:11 UTC 2018|
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.
|bf||Thu Nov 15 16:34:44 UTC 2018|
|bf||Wed Nov 14 21:00:30 UTC 2018|
|bf||Wed Nov 14 20:32:28 UTC 2018|
|bf||Thu Nov 15 15:10:37 UTC 2018|
|bf||Wed Nov 14 15:10:45 UTC 2018|
|bf||Thu Oct 18 22:49:32 UTC 2018|
|bf||Wed Oct 31 16:07:55 UTC 2018|
Most error conditions reported by darcs are due to invalid input from the user, or indicate non-existence of things (patches, files, ...). It makes no sense for darcs to take the blame for that, which is what the phrase suggests to me.
|bf||Thu Oct 4 23:39:19 UTC 2018|
This hint was probably added when we changed the default for push and pull to --no-set-default, so that users could get used to the new behavior. This has been many years ago and the hint nowadays looks rather strange and just causes confusion for newcomers or casual users. A by-product of this change is that the code for handling --set-default gets a lot simpler.
|bf||Sat Sep 29 20:03:30 UTC 2018|
This hint serves no purpose at all. We already told the user the name of the repo and that we don't recognize it as one. What more is there to say?
|bf||Sat Sep 29 20:16:18 UTC 2018|
First, it no longer shouts at the user. Second, instead of saying what the user "should probably" do, we give a clear recommendation, but make it conditional on circumstance (the user may want to keep the source if they plan to restore access to it).
|bf||Sat Sep 29 16:42:18 UTC 2018|
Since we use anchorPath "" now to convert AnchoredPath back to FilePath, we must not 'drop 2' from the result.
|bf||Mon Oct 22 10:01:52 UTC 2018|
The options are: ccApply, reply, happyForwarding and were supported by the apply and push commands. This patch removes all conditional compilation from Darcs.Util.Compat. It also removes the dependency on the random package when building for Windows.
|bf||Fri Oct 12 23:09:27 UTC 2018|
Swapping the order of the cases and then trying to pull out applyTreeFilter relevant made it apparent that (a) using the index in the IgnoreIndex case can be replaced by passing the pending_tree instead, and (b) applyTreeFilter relevant was missing in the UseIndex+ScanKnown case.
|bf||Tue Oct 2 21:26:43 UTC 2018|
|bf||Sun Oct 28 13:47:18 UTC 2018|
This was broken by patch e8d4e47572b175ea769524d5e09b86464eba7a4e * fix: fail if pending patch cannot be parsed
|bf||Sun Oct 21 22:00:11 UTC 2018|
The two global variables are reachableSourcesList and badSourcesList and they are exclusively used by D.R.Cache. So it seems cleaner to me to encapsulate them in the same module. They use MVars now to make access thread safe. While apparently the code seems to work with IORefs, the cache functions /are/ used from multiple threads, so MVars are the safer option.
|bf||Sat Sep 29 16:35:53 UTC 2018|
|bf||Thu Oct 11 07:49:25 UTC 2018|
|bf||Mon Oct 1 08:46:04 UTC 2018|
This is exactly the same as the chapter in the manual, slightly re-formatted for terminal output.
|bf||Sun Sep 30 17:27:51 UTC 2018|
The information given there was partly out-dated.
|bf||Sat Sep 29 11:23:00 UTC 2018|
|bf||Fri Oct 12 23:17:28 UTC 2018|
|bf||Fri Oct 12 21:36:58 UTC 2018|
This extension is already globally activated in the cabal file.
|bf||Fri Oct 12 21:27:55 UTC 2018|
|bf||Mon Oct 8 17:23:06 UTC 2018|
|bf||Sun Sep 30 21:06:35 UTC 2018|
|bf||Sun Sep 30 17:26:56 UTC 2018|
- page 1 of 416
- next ->