Re: [darcs-users] roadmap / priorities for Darcs (2016 edition!)
Hi Alexander, Darcs currently does not support signing data inside of repositories. It does only provide *patch bundle* signing in the "darcs send" command and checking the signature in "darcs apply". Now, patch signing in Darcs seems dificult to implement because context changes modify the actual contents of patches. That is, for a given patch, there are many possible contexts for it. In theory it would be possible to sign any patch by finding its minimal context and signing its contents against that context, maybe that would be too slow to compute for practical uses, or maybe not. What I think would be easier to do, would be signing tags. Since tags have no content, the idea would be to sign the pristine tree associated to some tag, and the signature would be written in the long description of the tag. Guillaume 2016-09-08 17:21 GMT-03:00 Alexander Berntsen: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > As a lowly wannabe user, I have one request. I want to verify that > things have been OpenPGP signed, e.g. with 'darcs log'. See 'git log > - --show-signature' for an example. I just want better OpenPGP-interop > in general. If satisfactory OpenPGP-interop is been achieved, I will > have no qualms just using darcs for my everyday work. > > Thank you for your consideration. > - -- > Alexander > alexan...@plaimi.net > https://secure.plaimi.net/~alexander > -BEGIN PGP SIGNATURE- > Version: GnuPG v2 > > iQIcBAEBCgAGBQJX0cgxAAoJENQqWdRUGk8BTsYP/0IRxSCc7GX6yDrhNndTzDic > BcqywCSy/mn92dWeZE/LNNYRrCHmU5n8lkHo1S1Ic1Az8JUD7BwuNwfNEY+yX+f0 > cqe2VWWgGzNel3WHNLHktsTLx4KMd3Hp0hb+9wIGH72JprvA3/IKE300oX68Mmep > vOzG7dzplv3RAm+tTWaQMat/SVTfG66b17ZW7IJ4kCGTUYnYkbEIMXkt2b5TShRD > zCn1y7u7cixAMD2dc8akwHR/Zs22swk3xTUFXuYYJRxUwS036++IRYQvzOhrg7/1 > PpJBvPsiWinL2ca4RyO9jqm5DdhLLYj3bRyrPn4SOze447Td63lYdAECBwhvbigX > JmP3f+uCrJPDDq3WSqciJYO1uFZy6A9psq7uaN5LdMCRLTBePFXTYUyOypVpdd3/ > xZ1WstSvrFFQTRVJ/6Px6lo77dDYvWE1NQLEAEHUpzykP4KZXXGnSEiq+7mK1P/w > cONBNy/ijHKxsJQS494JY96XktrP8SO5RiMEEE64ILi/Ug5GLQZsdZLUlLsL9hD8 > iWOHr78ni7q1t3X1+9w2cBUR578SHIAHFOG4jNbAO1BIeP44jJsWvBPFWgLyw25Y > XTExMzxR29AhCDPRU8ghwxKo7XNOt4O8L1J1B/gt+QkcQeGJl2beLKAgHg0IV61b > ASpOvXF3P74YdMRXk8ga > =lq/V > -END PGP SIGNATURE- > ___ > darcs-users mailing list > darcs-users@darcs.net > http://lists.osuosl.org/mailman/listinfo/darcs-users ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] roadmap / priorities for Darcs (2016 edition!)
HI all, Although it is uncertain at which rate Darcs' development is going to happen in the next months, I'd like to make a little summary of what we could do now: * since we now require GHC >= 7.10 we can grep through the TODO's in the source code and try to fix those that wish for new GHC features * also, can we simplify Darcs.Prelude? * we should investigate if closed type families (present since GHC 7.8) can simplify type witnesses ( http://irclog.perlgeek.de/darcs/2013-07-24#i_7366568 ) * interaction with VCS front-ends: I fixed Darcs support in Meld and DIffuse this year (stable release of Diffuse pending), we should look at the Geany VCS plugin, and maybe RabbitVCS, which is the other relevant front-end I know of. * once again: a manual... I am glad we did some simplification in Darcs' set of features before the release of 2.12 so we now have a more consistent set of commands, patterns and environment variables. I have a "genManual.sh" script on my computer that mixes the output of `darcs help markdown` and some wiki pages, and generates a manual in several formats (HTML, PDF, EPUB) thanks to pandoc. If anyone is interested we may just start working on it on a hub.darcs.net repo. thanks, Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] [ANN] Darcs 2.12.1 release
Hi all, The Darcs team is pleased to announce the release of Darcs 2.12.1. The most important changes are: * fixes for building with GHC 8 * drop support for GHC 7.6 and 7.8, i.e., require GHC 7.10 * improvements in `darcs whatsnew` output with irrelevant files (Ben Franksen) This release can be installed via cabal or (soon) stack. The 2.12 branch is also available as a darcs repository from http://darcs.net/releases/branch-2.12 . Thanks! Guillaume Hoffmann ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] diff algorithm: matching similar lines
Ah :) Yes, what you described would be an "ideal" patch for that case. ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] diff algorithm: matching similar lines
In the example you gave, "darcs record" just removes the "a" line (current or old diff algorithm). ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] diff algorithm: matching similar lines
Hi Henning, You are right saying that Darcs matches exactly equal lines. I'm afraid that what you are proposing is not possible with Darcs' current internal representation of patches. Darcs handles patches in a line-based way. So the problem is worse than computationnal cost. But a future and incompatible version of Darcs could support indentation patch type. Indeed the code of Darcs currently works with a current set of patch types but can adapt to another one at the expense of breaking compatibility with existing repositories. There have been a few proposals about new patch types but for now no concrete roadmap for a switch. Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] [ANN] Darcs 2.12.0 release
Hi all, The Darcs team is pleased to announce the release of Darcs 2.12.0. # Downloading # One way of installing Darcs 2.12.0 is with stack: $ stack install darcs-2.12.0 Or first install the Haskell Platform (http://www.haskell.org/platform) and install Darcs with cabal-install: $ cabal update $ cabal install darcs-2.12.0 You can also download the tarball from http://darcs.net/releases/darcs-2.12.0.tar.gz and build it by hand. The 2.12 branch is also available as a darcs repository from http://darcs.net/releases/branch-2.12 # What's new since Darcs 2.10.3 # ## New features ## * `darcs show dependencies`: export patch dependency graph as dot file (Ale Gadea) ## User Interface ## * improvements in `darcs record` output with irrelevant files (Ben Franksen) * `darcs log -v --machine-readable`: show internal representation of patches (including explicit dependencies). Remove patch viewing via the "darcs annotate" command. (Guillaume Hoffmann) * `whatsnew -s` (and `status`) show conflicting files (Guillaume Hoffmann) * honor "quiet" flag in command outputs (Ben Franksen) * a single `show patch-index` command (Guillaume Hoffmann) * remove deprecated aliases of show (Guillaume Hoffmann) * remove hack to enable arbitrary protocols via env variables (Guillaume Hoffmann) ## Performance ## * handle file moves natively when importing from git (Owen Stephens) ## Developer-related ## * require GHC 7.6 (base > 4.6) and support GHC 8 (Ganesh Sittampalam) * switch to sandi from dataenc (Daniil Frumin) * refactoring to prepare stash (Ganesh Sittampalam) * change argument order of type witness RL (Ben Franksen) * Darcs.Repository / repository cloning refactoring (Ben Franksen) * use of async when cloning with packs (Ben Franksen) * SSH code refactoring (Ben Franksen) * Patch and RealPatch renamed to RepoPatchV1 and RepoPatchV2 (Guillaume Hoffmann) * merged hashed-storage into libdarcs and hashed-storage tests into darcs-test (Guillaume Hoffmann) * reorganize Darcs.Repository.* modules (Guillaume Hoffmann) ## Issues resolved in Darcs 2.12 ## * issue1807: clarify help of PAGER, DARCS_PAGER (Guillaume Hoffmann) * issue2258: improve patch index error message with suggestion (Guillaume Hoffmann) * issue2269: push hijack test to suspend time (Eric Kow) * issue2276: Keep track of patch hijack decisions (Eric Kow) * issue2138: report conflicting files in whatsnew -s (Guillaume Hoffmann) * issue2393: remove whatsnew functionality from annotate (Guillaume Hoffmann) * issue2400: use async package to keep track of unpack threads (Ben Franksen) * issue2459: fall back to writing the file if createLink fails (Ben Franksen) * issue2479: root dir most not be among the sources of a move (Ben Franksen) * issue2481: expose API for 'darcs diff' command (Ganesh Sittampalam) * issue2486: obliterate --not-in-remote -q should be more quiet (Ben Franksen) * issue2489: dequote filepaths while importing from git (Guillaume Hoffmann) * issue2494: output of darcs record with file arguments (Ben Franksen) Thanks! Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] plans for Darcs 2.12
Hi, the 2.12 branch is available at http://darcs.net/releases/branch-2.12 Supported GHC versions are from 7.6 to the latest 8 rc3 (thanks to patches by Ganesh). Testers are welcome! The current target release day is thursday 28/4. Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] Darcs News #113
# News and discussions 1. We will release Darcs 2.12 by the end of this month: - <http://lists.osuosl.org/pipermail/darcs-users/2016-April/027198.html> - <http://darcs.net/Releases/2.12> 2. On May 6th-8th in Helsinki, a joint sprint Pijul/Darcs is organized: - <http://lists.osuosl.org/pipermail/darcs-users/2016-April/027197.html> - <http://darcs.net/Sprints/2016-05> # Issues resolved (5) issue1807 Guillaume Hoffmann ~ - clarify help of PAGER, DARCS_PAGER - <http://bugs.darcs.net/issue1807> issue2258 Guillaume Hoffmann ~ - improve patch index error message with suggestion - <http://bugs.darcs.net/issue2258> issue2393 Guillaume Hoffmann ~ - remove whatsnew functionality from annotate - <http://bugs.darcs.net/issue2393> issue2486 Ben Franksen ~ - obliterate --not-in-remote -q should be more quiet - <http://bugs.darcs.net/issue2486> issue2494 Ben Franksen ~ - output of darcs record with file arguments - <http://bugs.darcs.net/issue2494> # Patches applied (96) 2016-04-14 Guillaume Hoffmann ~ - move network-related tests to network dir, update command names - resolve issue2393: remove whatsnew functionality from annotate - add log --machine-readable to see patch dependencies non-interactively - help of log 2016-04-01 Ganesh Sittampalam ~ - add some doc comments to RepoType 2016-03-29 Guillaume Hoffmann ~ - merge Repository.Util into Repository.State - use B and BC instead of BS and BSC in Repository.State - fix prelude import in Repository.State - move maybeApplyToTree to Darcs.Patch.Apply - move getRecursiveDarcsRepos to UI.Commands.Optimize - move patchSetfMap to Darcs.Patch.Set - move functions from Repository.Util to Patch.TokenReplace - comment in Repository.Util - refactor similar functions in Darcs.Repository.State - use readUnrecordedFiltered in getReplaces - inline a function in Clone - no longer move index to index.old on mingw32 os - clarify comments in Darcs.Repository.State - hlint Darcs.Repository.State - move External module from Repository to Util - move Compat and Lock modules from Repository to Util - merge Darcs.Repository.Ssh into Darcs.Util.Ssh - remove Darcs.Repository.Read by moving readRepo back to Internal - add comments and remove checks of optimize commands wrt repo formats - make all optimize subcommands require hashed except upgrade - move copySources from HashedRepo to Clone - move Storage.Hashed modules to Darcs.Util - remove unused function from Storage.Hashed.Plain - fix compile error in Storage.Hashed.Test - remove Storage.Hashed.Utils, move functions to Darcs.Utils.ByteString - move index-related functions from Utils to Index - removed unused or redundant functions from Storage.Hashed.Utils - remove unused functions from Storage.Hashed.Hash - hlint Storage.Hashed.Darcs - reuse functions from Darcs.Util.Path - remove unused Storage.Hashed.Packs 2016-03-09 Ben Franksen ~ - revert command: be quiet when requested - accept issue2480: display unicode in patch content - slightly improved chaotic indentations and import lists - refactor: use maybeRestrictSubpaths - refactor: use Darcs.Util.English.capitalize - replace Darcs.Util.Printer.<> with <> from Data.Monoid; restructured haddocks - small code layout fix in whatsnew command - fixed Darcs.Util.English.andClauses and orClauses - two simple refactorings in the conflict resolution code - cleanup in revert command: use debugMessage for debug messages - cleanup: break over-long line in D.R.Merge - accept issue2494: output of darcs record with file arguments - resolve issue2494: output of darcs record with file arguments - refactored some, added readUnrecordedFiltered and maybeRestrictSubpaths - several fixes and refactorings in fixSubPaths and maybeFixSubPaths - add Darcs.Util.Printer.quoted and Darcs.Util.Text.pathlist - added missing hsep function to D.Util.Printer - added missing Eq and Show instances for ScanKnown - added Darcs.Util.Printer.ePutDocLn - add new type IncludeBoring for includeBoring option (was Bool) - announceFiles only if verbosity /= Quiet 2016-03-05 Guillaume Hoffmann ~ - rm hashed-storage changelog - put copyright headers in hashed-storage modules - add Storage/Hashed dir to checkdeps contrib script - merge Storage.Hashed.AnchoredPath into Darcs.Util.Path - explicit exports for Storage.Hashed.Utils - list and comment exports of Storage.Hashed.Darcs and Plain - remove Storage.Hashed - resolve issue2258: improve patch index error message with suggestion - resolve issue1807: cla
Re: [darcs-users] plans for Darcs 2.12
In the light of the next Darcs/Pijul sprint, and in the light of the lack of GHC 8 (yet), I would like to release Darcs 2.12 by the end of this month. My current plan is: * Thursday 21st of April : clone branch-2.12 from reviewed * Some day until (and including) Friday 29th of April: unleash Darcs 2.12.0 ! The current status of the release is: http://darcs.net/Releases/2.12 (see also http://tinyurl.com/darcs2-12bugs ). When we need to adjust some details for GHC 8 we'll do a 2.12.1 release. Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] darcs news #112
# News and discussions 1. After 7 years of being the maintainer/Benevolent Dictator of Darcs, Eric Kow stepped down and offered me (Guillaume Hoffmann) to take over, which I accepted: - <http://lists.osuosl.org/pipermail/darcs-users/2015-October/027144.html> - <http://lists.osuosl.org/pipermail/darcs-users/2015-October/027145.html> 2. The release process of Darcs 2.12 will start when GHC 8 is released: - <http://lists.osuosl.org/pipermail/darcs-users/2016-March/027185.html> 3. We had two new minor releases of Darcs 2.10, and in spite of being minor, they contain a few interesting changes and optimizations: - <http://lists.osuosl.org/pipermail/darcs-users/2015-November/027151.html> - <http://lists.osuosl.org/pipermail/darcs-users/2016-January/027182.html> 4. In a span of 4 months we had two sprints, one in Paris in September and another another in Seville in January, check out the reports: - <http://blog.darcs.net/2015/09/darcs-hacking-sprint-9-report.html> - <http://blog.darcs.net/2016/01/darcs-hacking-sprint-10-report.html> 5. Finally, Pierre-Étienne Meunier announced a Pijul sprint in may in Finland. Darcs hackers are welcome! -<http://pijul.org/2016/03/16/sprint.html> # Issues resolved (7) issue2269 Eric Kow ~ - push hijack test to suspend time - <http://bugs.darcs.net/issue2269> issue2276 Eric Kow ~ - Keep track of patch hijack decisions - <http://bugs.darcs.net/issue2276> issue2400 Ben Franksen ~ - use async package to keep track of unpack threads - <http://bugs.darcs.net/issue2400> issue2459 Ben Franksen ~ - fall back to writing the file if createLink fails - <http://bugs.darcs.net/issue2459> issue2479 Ben Franksen ~ - root dir most not be among the sources of a move - <http://bugs.darcs.net/issue2479> issue2481 Ganesh Sittampalam ~ - expose API for 'darcs diff' command - <http://bugs.darcs.net/issue2481> issue2489 Guillaume Hoffmann ~ - dequote filepaths while importing from git - <http://bugs.darcs.net/issue2489> # Patches applied (176) 2016-03-26 Sergei Trofimovich ~ - allow zip-archive-0.3 2016-03-22 Guillaume Hoffmann ~ - remove failing-issue1609 from testsuite as property we don't want 2016-03-06 Ben Franksen ~ - move command: fixed punctuation of error messages and added a comment - use bug from impossible.h instead of error - cleanup in Darcs.Patch.Merge: use case instead of fromJust (do return ...) 2016-02-12 Ganesh Sittampalam ~ - Get rid of the need for DummyPatch in Darcs.Patch.Match 2016-03-05 Guillaume Hoffmann ~ - move runHLint.sh to root and update to run outside of testsuite 2016-02-12 Ganesh Sittampalam ~ - drop re-exports from Darcs.Patch.Rebase - abstract out checking whether a Named is internal - add versions of simplifyPush[es] for Suspended - move addFixup to Rebase.Container and give it a clearer name - add Repair instance for Suspended - Ignore the rebase internal patch when showing dependencies - simplify instance ShowPatchBasic (RebaseSelect p) - break out PatchInspect instance for Suspended - rename mkSuspended to mkRebase and make it work on 'Suspended' - use Suspended instead of FL RebaseItem in take*Rebase* - break out RepairToFL instance for Suspended - break out ReadPatch instance for Suspended - break out Check instance for Suspended - break out Show instances for Suspended - break out Conflict instance for Suspended - break out Effect instance for Suspended - add PrimPatchBase instance for Suspended - break out ShowPatch instance for Suspended - break out Apply instance for Suspended - refactor instance ShowPatch Rebasing a bit - inline a couple of defaults to simplify future refactoring - abstract out an instance ShowPatchBasic Suspended - Introduce a 'Suspended' type to encapsulate 'FL RebaseItem' 2016-03-18 Ben Franksen ~ - skip ssh tests if ssh server is down - made network ssh tests more robust by passing --skip-long-comment - fix ssh network tests so they work in the test harness - skip http network tests when server does not respond - run network tests by default - resolve issue2479: root dir most not be among the sources of a move - accept issue2479: bug descending in modifyTree 2016-03-08 Guillaume Hoffmann ~ - update failing-issue2219 - acknowledge that issue1196 is solved - acknowledge a working case in failing-index-argument.sh - merge HACKING into README.md 2016-02-17 Ganesh Sittampalam ~ - get rid of a couple of trailing newlines 2016-02-05 Guillaume Hoffmann ~ - remove unused executable and testsuite dependencies - comment in cabal file workaround
Re: [darcs-users] plans for Darcs 2.12
Thanks for testing with GHC8! OK for stash; I agree to favour a sound release date over having a particular feature included in 2.12. Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] plans for Darcs 2.12
Hi everyone, we had an important release of Darcs 2.10.0 on April of 2015, and the last point-release is 2.10.3 from January of 2016. I'm aiming at releasing Darcs 2.12 whithin the next couple of months to avoid waiting too long for another "big release" which would cost us too much effort. I think the only blocker for the release is "darcs stash". Ganesh has already sent many patches for a refactoring that prepares the stash command and there are more coming. We need to review them and test the feature when it is done. Ganesh also has improvements for the "darcs test" command, if they can be ready soon, they will make it in 2.12. If anyone else thinks about another important feature to get in, please let me know. The perfect moment for the release would be not too long after the release of GHC 8, so that we can hope to have Darcs 2.12 included in the next Debian stable along with GHC 8. Opinions? Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] darcs 2.10.3 release
The darcs team is pleased to announce the release of darcs 2.10.3 ! # Downloading # One way of installing Darcs 2.10.3 is with stack: $ stack install darcs-2.10.3 Or first install the Haskell Platform (http://www.haskell.org/platform) and install Darcs with cabal-install: $ cabal update $ cabal install darcs-2.10.3 You can also download the tarball from http://darcs.net/releases/darcs-2.10.3.tar.gz and build it by hand. The 2.10 branch is also available as a darcs repository from http://darcs.net/releases/branch-2.10 # What's new in 2.10.3 (since 2.10.2) # * implement weak repository hash and show it in "darcs show repo" * implement "whatsnew --machine-readable" for more parsability * enhance Git import: empty directories, unescape file names, unnamed commits * make commit an alias for record * expose API for "darcs diff" * force grep to treat output of locale as text * bump dependencies: vector, process, HUnit, binary, transformers, time, HTTP, transformers-compat # Feedback # If you have an issue with darcs 2.10.3, you can report it on http://bugs.darcs.net/ . You can also report bugs by email to b...@darcs.net, or come to #darcs on irc.freenode.net. ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] Maintaining a history of compilable repository states
> I assumed that 'darcs test' is the replacement 'darcs check --test', isn't > it? 'darcs test --help' says that '--once' is the default. Ok, but I was not > aware, that 'darcs test' also replaces 'trackdown'. You're right and I was wrong! "darcs test" is indeed the replacement of "darcs check --test". "darcs test --linear" is the replacement of "darcs trackdown". Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] Maintaining a history of compilable repository states
Hi Henning, > Older darcs versions (e.g. darcs-2.5) had the 'trackdown' function. > http://darcs.net/manual/Darcs_commands.html#SECTION006112000 > > It seems to be removed in darcs-2.10. I wonder how it can work if many > interim states do not compile. It is present in 2.10 under the command "darcs test". Its default behaviour is the same as the old "darcs trackdown" but it also has "darcs test --bisect" and "darcs test --backoff". See http://darcs.net/Using/Test (And sorry about the manual being outdated, we'll try to fix this soon.) > What ideas or proposals do you have for reconstructing historic repository > states and make 'trackdown' actually work? Maybe it would help to somehow > mark patch sets that once in time succeeded to run a 'darcs test'. I should > also be able to mark patch sets manually in case I cannot run a test > temporarily (changes in versions of dependent libraries and compilers). One way of improving the situation would be to improve the command "darcs test" itself so that it navigate better in the space of previous versions. I know that Ganesh has a work-in-progress patch to enhance Darcs in this way (for instance, Ganesh's work would make "darcs test" aware of unbuildable states, instead of treating them as "failing"). Another way I can think of is to maintain some external repo-state -> test-result mapping and maintain that information at the level of a project. Recently we had a "weak repository hash" feature added to Darcs and it will be part of the next 2.10.3 release (it's the hash that appears at the last line of "darcs show repo" at http://lpaste.net/8869552059779645440 ). Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] Darcs Hacking Sprint #10 (January 15th-17th, Seville)
Dear hackers, happy new year to everyone! This is a reminder for the people interested in participating. Please contact us ASAP so that we can grant you access to the university during the weekend. See http://wiki.darcs.net/Sprints/2016-01 . Thanks Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] repository state identifier(s) in "darcs show repo"
2015-12-15 17:18 GMT-03:00 Ganesh Sittampalam: > I think showing the XORed hashes is a good idea. We've previously held > back because of not being able to do the reverse mapping easily, but > something is better than nothing. I looked but haven't found previous discussion about this. > There's some discussion of using XOR on this StackOverflow post: > > http://stackoverflow.com/questions/5889238/why-is-xor-the-default-way-to-combine-hashes > > The two main criticisms of XOR there are that it doesn't preserve > ordering (which for us is a feature), and that XORing two identical > things gives a 0. I don't think we'll have two identical patch hashes in > the same repo, so that also seems fine. Agreed. > One thing to make very clear: these hashes will *not* be secure - as you > can fake any patch with the right metadata but wrong content. Yes. We can cite http://robotics.stanford.edu/~xb/crypto06b/index.html . > I'm not too keen on showing the pristine hash. I guess a good point of > comparison here would be git: does it ever expose just a tree hash (as > opposed to the full commit id)? Indeed, it seems really to be an internal hash, so far. Maybe for a buildbot system it can be useful to expose it since two identical pristine hashes are really two equal working copies. Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] repository state identifier(s) in "darcs show repo"
More info about the different hashes that Darcs uses: http://darcs.net/Internals/Hashes The XOR I propose is on hash #1. ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] repository state identifier(s) in "darcs show repo"
Hi everyone, As said by David Leuschner in a previous mail, one of the shortcomings of Darcs is: "it's not as easy to refer to a specific state of the repository using a hash". As a developer I know that Darcs uses (internally) the pristine hash, which is a hash of the recorded working copy. However two repositories can have the same pristine hash and different histories (eg, one being a superset of the other with patches and their corresponding rollbacks, or one having tags that the other lacks). But it can be good enough for some purposes (lazy cloning). Should "darcs show repo" show that hash? Now most importantly, we need a hash that would identify a set of patches independently of reordering, since it's what Darcs considers the history of a repository. Doing it right, eg building and hashing the dependency graph of all patches, is costly. Moreover we do not have any infrastructure to retrieve a set of patches from such hash. (That's the scenario in http://darcs.net/Ideas/ShortSecureId ). So can we just have one that would enable us to quickly check that two repos have the same patches, ignoring reordering? I propose a simple checksum: XOR all patch metadata hashes! Probability of collision should be low enough since patch metadata hashes are good hashes. Calculating the XOR is as fast as reading the inventories of the current repo (which can be lazy) plus the overhead of generating and XOR'ing the hashes. Darcs itself would not need to store this XOR, it seems. But there could be many uses of it by third-party tools, on the other hand. Darcsden could show it for comparison purposes. A development team could maintain a XOR-to-patchset map to identify repository states encountered by its members. Let the tools emerge later! So, should "darcs show repo" show that XOR? Opinions? Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] Darcs Hacking Sprint #10 (January 15th-17th, Seville)
Dear Hackers I'm glad to announce that the 10th Darcs Sprint that will be in Seville, on January 15-17 at the ETS de Ingeniería Informática, Universidad de Sevilla. Please check the details at: http://darcs.net/Sprints/2016-01 Here are three things to know 1. Everybody is welcome to join us. We'd love to have you, whatever your Haskell or Darcs hacking experience. Also, if you've got a wacky idea for the future of version control, or a cool use for the Darcs library, you should join us too :-) 2. Please let us know if you're attending: * add your name to http://wiki.darcs.net/Sprints/2016-01 * send me (privately) your full name and some official identification number for access to the university on Saturday and Sunday. 3. We can reimburse travel costs (within reason!). Let us know if you'd like a reimbursement, and save your receipts. Many thanks to everybody who participated in our fundraising drives or who gave money on the side. Thanks also to the Software Freedom Conservancy for making fundraising and reimbursements so painless! If you can't join us in person, but you'd like to cheer us on, say hello at http://darcs.net/Donations ! see you in one month! Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] darcs 2.10.2 release
The darcs team is pleased to announce the release of darcs 2.10.2 ! # Downloading # The easiest way to install darcs 2.10.2 from source is by first installing the Haskell Platform (http://www.haskell.org/platform). If you have installed the Haskell Platform or cabal-install, you can install this release by doing: $ cabal update $ cabal install darcs-2.10.2 Alternatively, you can download the tarball from http://darcs.net/releases/darcs-2.10.2.tar.gz and build it by hand as explained in the README file. The 2.10 branch is also available as a darcs repository from http://darcs.net/releases/branch-2.10 # What's new in 2.10.2 (since 2.10.1) # * optimize patch apply code memory use * make patch selection lazier in presence of matchers * switch patches retrieval order when using packs * switch from dataenc (deprecated) to sandi * finish updating help strings with new command names * clean contrib scripts * disable mmap on Windows * enhance darcs send message * fix quickcheck suite * shorter README with quickstart instructions * fixed the following bugs: * 2457: fix darcs-test command line options * 2463: building darcs on powerpc * 2444: added default interactivity parameter to isInteractive # Feedback # If you have an issue with darcs 2.10.2, you can report it on http://bugs.darcs.net/ . You can also report bugs by email to b...@darcs.net, or come to #darcs on irc.freenode.net. ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] new darcs maintainer: Guillaume Hoffmann
Hi David, > At the moment I don't really know what to expect from Darcs. The Darcs > development team is passionate and highly competent but very small. I also > don't know what the direction will be. What are the major improvements > you'd all like to work on? Right now, I'm not working on any major improvement but rather seeing what should go into the next release, which I'd like to do next February. It will probably not have any new killer feature and will be mostly code improvements with some visible improvements (hopefully we'll solve the "couldn't fetch" bugs this time!). Also it is good to regularly keep up with new GHC releases. In parallel I'd like to have students work on projects. I put online the following Projects page: http://darcs.net/Projects , which would be for any kind of student projects, not only GSoC. > From the top of my head the perceived shortcomings of previous Git users are > - switching branches is not possible within the same directory [...] +1 See http://bugs.darcs.net/issue555 for an old discussion about this and a shell script that "implements" this feature, while we wait for Ganesh's stash implementation :) > - it's not as easy to refer to a specific state of the repository using a > hash I'd like to see progress on this issue, within the possibilities of darcs' current repo format. See http://bugs.darcs.net/issue992 and http://darcs.net/Ideas/ShortSecureId Or maybe can we use darcsden somehow to store more information about repositories? > - when merging conflicts it's difficult to understand which part of the > marked conflict belongs to which patch See http://bugs.darcs.net/issue833 Ganesh did some work on this: http://hub.darcs.net/ganesh/darcs-conflict-marking I remember Ganesh said it was inefficient, but anyway I wonder if we can have this into 2.12 ? > - I'd like to amend-record a patch that other patches depend on (without > having to suspend, amend-record, unsuspend) I wonder if we can have such detection of cases where rebasing can be automatic? It would definitely be great to have! thanks for the feedback David! Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] pre-sprint survey: changes that should go into darcs 2.10.2
An update, here are the patches that are currently accepted for darcs 2.10.2 are: * remove redundant import * drop sandi lower bound to support GHC 7.4 and add an upper bound * Switch from dataenc (deprecated) to sandi * replace changes by log in two help strings * make patch selection lazier in presence of matchers * resolve issue2444: added default interactivity parameter to isInteractive * resolve issue2463: building darcs on powerpc * resolve issue2457 (replace --diffalgorithm and --repoformat with single flags) * require text>=1.2.1.3 if using ghc 7.10 * require text>=1.2.1.2 if using ghc 7.10 * Add missing file for 'renames.sh' test ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] new darcs maintainer: Guillaume Hoffmann
Hi everyone, I guess I should say a few words about this :-) First I'd like to thank Eric for his work as a maintainer for 7 years, and hope he'll stick around! For the observers that might wonder what is going to change for the Darcs project, the answer is: not much. Ever since I started participating to Darcs (2009, my first sprint attendance :,-) ), I found the project to be very collaborative and consensus-lead. Anyone is welcome to send patches, code reviews are public and are a great opportunity to learn about Darcs' codebase; release management duties have been shared between several members over time; coding sprints are open for participation, and indeed, every time we have a few non-darcsers visiting us and helping. I am very happy with these aspects of Darcs as a free software project, and Eric ensured all of this happened over the years. So, things will continue as before! As for Darcs the software, how is it going to evolve? I cannot answer this question alone for the long term. What I can say, is that in the past I sometimes found Darcs' evolution as being a little too slow and conservative. We lost valuable energy and focus in decisions which did not pay off eventually. On some topics we did not reach any conclusion and sticked to the status quo. My guess is that this drove a few hackers to stop contributing, while the users also left anyway! I don't mean that we're going to break everything just to make us developers happy. The very nature of Darcs leads us to be conservative: Darcs is not just a software but also a data format (Darcs repositories) which we don't want to change unless we have a *really* good reason to do so. Also, Darcs handles other people's data, so we want it to be safe and predictable. On the other hand, I think we should really commit to the transitions we set ourselves to do, and remember that developer energy is a scarce resource. Now for the short term, what is going to happen? We had a big 2.10 release last April, 3 years after 2.8. It included a lot of new stuff, which made us very happy; but the release process was consequently quite long. I'd like the next release to happen sooner and I propose myself to take care of it for a second time. The release process will start after the GHC 8 release and the next sprint, which means February. Happy hacking! Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] Darcs Hacking Sprint #9 (September 18th-20th, Paris)
Just a reminder that the next Darcs sprint is *this weekend* from Friday to Sunday in Paris. Have a look below for more details! 2015-08-21 15:58 GMT-03:00 Guillaume Hoffmann <guilla...@gmail.com>: > Dear Hackers > > the next Darcs Sprint that will be in Paris, on September 18-20 at > IRILL (near Place d'Italie). > > Please check out the details at: > > http://darcs.net/Sprints/2015-09 > > Here are three things to know > > 1. Everybody is welcome to join us. We'd love to have you, whatever >your Haskell or Darcs hacking experience. Also, if you've got a >wacky idea for the future of version control, or a cool use for the >Darcs library, you should join us too :-) > > 2. Please let us know if you're attending. Just add your name to >http://wiki.darcs.net/Sprints/2015-09 and you're good to go. >You can also send us an email. > > 3. We can reimburse travel costs (within reason!). Let us know if you'd >like a reimbursement, and save your receipts. > >Many thanks to everybody who participated in our fundraising drives >or who gave money on the side. Thanks also to the Software Freedom >Conservancy for making fundraising and reimbursements so painless! >If you can't join us in person, but you'd like to cheer us on, >say hello at http://darcs.net/Donations ! > > see you in one month! > > Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] pre-sprint survey: changes that should go into darcs 2.10.2
Hi, I'd like to know if people needed a darcs 2.10.2 release soon, and if there are changes/bugs that we should particularly look at? Since we're doing the Hacking Sprint this weekend, we can have a look at the issues you think are most urgent. Don't hesitate to nag me by answering this mail (posting links to existing issues in the bug tracker, mail archive, etc.), even if it's information that was already posted/discussed elsewhere. Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] Darcs News #111
# News and discussions 1. The next Darcs Sprint will take place in Paris on September 18-20th. Please add yourself to the wiki page if you're going! - <http://lists.osuosl.org/pipermail/darcs-users/2015-August/027134.html> - <http://darcs.net/Sprints/2015-09> 2. Darcs 2.10.1 has been released (bugfixes, dependency versions bump): - <http://lists.osuosl.org/pipermail/darcs-users/2015-July/027130.html> # Issues resolved (19) issue2102 Guillaume Hoffmann ~ - document packs in help of clone and optimize http - <http://bugs.darcs.net/issue2102> issue2307 Daniil Frumin ~ - Add information about 'darcs help manpage' and 'darcs help markdown' - <http://bugs.darcs.net/issue2307> issue2308 Ben Franksen ~ - use command agnostic comment for changes summary - <http://bugs.darcs.net/issue2308> issue2327 Alain91 ~ - ask user to keep trying if locking fails - <http://bugs.darcs.net/issue2327> issue2420 Ben Franksen ~ - commandGetArgPossibilities for apply should not list all files in the repo - <http://bugs.darcs.net/issue2420> issue2421 Guillaume Hoffmann ~ - don't fail if caches are not writeable - <http://bugs.darcs.net/issue2421> issue2423 Alain91 ~ - fix diff only respecting --diff-command when a diff.exe is present - <http://bugs.darcs.net/issue2423> issue2433 Guillaume Hoffmann ~ - fix help strings of send and fetch - <http://bugs.darcs.net/issue2433> issue2438 Guillaume Hoffmann ~ - no longer build patch index by default on cloning - <http://bugs.darcs.net/issue2438> issue2444 Ben Franksen ~ - added default interactivity parameter to isInteractive - <http://bugs.darcs.net/issue2444> issue2446 Guillaume Hoffmann ~ - in fast-export delete dirs before dumping contents - <http://bugs.darcs.net/issue2446> issue2447 Ben Franksen ~ - by using getNonrangeMatch as in ShowFiles - <http://bugs.darcs.net/issue2447> issue2448 Gian Piero Carrubba ~ - enable -h/--hash flag for the diff command - <http://bugs.darcs.net/issue2448> issue2449 Ganesh Sittampalam ~ - use new hook in shelly to handle test output as binary - <http://bugs.darcs.net/issue2449> issue2451 Ben Franksen ~ - allow terminfo 0.4.* - <http://bugs.darcs.net/issue2451> issue2457 Ben Franksen ~ - fix darcs-test command line options - <http://bugs.darcs.net/issue2457> issue2461 Ben Franksen ~ - this time also when no file names are specified - <http://bugs.darcs.net/issue2461> issue2461 Ben Franksen ~ - darcs log --repo=remoterepo creates and populates _darcs - <http://bugs.darcs.net/issue2461> issue2463 Joachim Breitner ~ - building darcs on powerpc - <http://bugs.darcs.net/issue2463> # Patches applied (145) 2015-06-28 Ben Franksen ~ - removed cleaning of _darcs/patches before getting patches pack 2015-07-30 Guillaume Hoffmann ~ - require text>=1.2.1.3 if using ghc 7.10 - require text>=1.2.1.2 if using ghc 7.10 2015-07-04 Ben Franksen ~ - extended network/log.sh test (repeat without any filename arguments) 2015-07-16 Joachim Breitner ~ - resolve issue2463: building darcs on powerpc 2015-07-02 Ben Franksen ~ - simplified code in D.R.Ssh by using withMVar - use transferModeHeader from D.R.Ssh in D.U.C.TransferMode - made connection caching in Darcs.Repository.Ssh thread safe 2015-07-17 Sergei Trofimovich ~ - Add missing file for 'renames.sh' test 2015-06-28 Ben Franksen ~ - cleanup in Darcs.Util.URL - cleanup: break up an over long code line D.R.Clone - cleanup: removed unnecessary LANGUAGE CPP pragma from D.U.C.TransferMode - cleanup: removed an unused export from Darcs.UI.Options.Matching - Darcs.Repository.Clone: removed useless haddocks for createRepository - Darcs.Repository.Clone: moved cleanDir to the top level - renamed option matchOne to matchUpToOne - refactored Darcs.Repository - resolve issue2457 - fixed comment: ammend does not use the matchOne option - added a test for issue2378 (no longer fails) 2015-07-09 Guillaume Hoffmann ~ - please hackage adding 'manual: True' to the warn-as-error flag 2015-06-22 Ben Franksen ~ - fix precondition violation in hashed-storage tests - resolve issue2461, this time also when no file names are specified - resolve issue2461: darcs log --repo=remoterepo creates and populates _darcs - extend network/log.sh test for things mentioned in issue2461 2015-07-03 Ganesh Sittampalam ~ - rollback issue2455 test - issue now resolved as invalid 2015-06-21 Ben Franksen ~ - accept issue2455: darcs record -la does not see a rmfile change 2015-06-28 Ganesh Sittampalam ~ - stop test being sensitive to runner
[darcs-users] Darcs Hacking Sprint #9 (September 18th-20th, Paris)
Dear Hackers the next Darcs Sprint that will be in Paris, on September 18-20 at IRILL (near Place d'Italie). Please check out the details at: http://darcs.net/Sprints/2015-09 Here are three things to know 1. Everybody is welcome to join us. We'd love to have you, whatever your Haskell or Darcs hacking experience. Also, if you've got a wacky idea for the future of version control, or a cool use for the Darcs library, you should join us too :-) 2. Please let us know if you're attending. Just add your name to http://wiki.darcs.net/Sprints/2015-09 and you're good to go. You can also send us an email. 3. We can reimburse travel costs (within reason!). Let us know if you'd like a reimbursement, and save your receipts. Many thanks to everybody who participated in our fundraising drives or who gave money on the side. Thanks also to the Software Freedom Conservancy for making fundraising and reimbursements so painless! If you can't join us in person, but you'd like to cheer us on, say hello at http://darcs.net/Donations ! see you in one month! Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] darcs 2.10.1 release
Hi all, The darcs team is pleased to announce the release of darcs 2.10.1 ! # Downloading # The easiest way to install darcs 2.10.1 from source is by first installing the Haskell Platform (http://www.haskell.org/platform). If you have installed the Haskell Platform or cabal-install, you can install this release by doing: $ cabal update $ cabal install darcs-2.10.1 Alternatively, you can download the tarball from http://darcs.net/releases/darcs-2.10.1.tar.gz and build it by hand as explained in the README file. The 2.10 branch is also available as a darcs repository from http://darcs.net/releases/branch-2.10 # What's new in 2.10.1 (since 2.10.0) # - generalized doFastZip for darcsden support - support terminfo 0.4, network 2.6, zlib 0.6, quickcheck 2.8 and attoparsec 0.13 - errorDoc now prints a stack trace (if profiling was enabled) (Ben Franksen) - beautified error messages for command line and default files (Ben Franksen) - fixed the following bugs: - issue2449: test harness/shelly: need to handle mis-encoded/binary data (Ganesh Sittampalam) - issue2423: diff only respecting --diff-command when a diff.exe is present (Alain91) - issue2447: get contents of deleted file (Ben Franksen) - issue2307: add information about 'darcs help manpage' and 'darcs help markdown' (Dan Frumin) - issue2461: darcs log --repo=remoterepo creates and populates _darcs (Ben Franksen) - issue2459: cloning remote repo fails to use packs if cache is on a different partition (Ben Franksen) # Feedback # If you have an issue with darcs 2.10.0, you can report it on http://bugs.darcs.net/ . You can also report bugs by email to b...@darcs.net, or come to #darcs on irc.freenode.net. # Known issues # - issue2269: rebase should warn about stolen patches at suspend, not unsuspend - issue2272: darcs rebase unsuspend should automate or semi-automate handling unrecorded changes - issue2276: darcs rebase unsuspend needs UI improvements for You are not... Amend anyway? - issue2359: convert --export mishandles Unicode filenames - issue2372: Please remove HINT: I could not reach... message - issue2436: rollback --patches takes ages before first prompt - issue2445: internal error if suspended patch is pulled into repository again ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] imminent 2.10.1 release
Dear Darcsers, I'm planning to release Darcs 2.10.1 soon, which contains a few bugfixes and dependency version bumps. If you want to help, please get, build and test the 2.10 branch from over there: * darcs clone: http://darcs.net/releases/branch-2.10/ * zip download: http://darcs.net/releases/branch-2.10/branch-2.10.zip * darcs clone from hub.darcs.net mirror: http://hub.darcs.net/darcs/darcs-2.10/changes What's new in 2.10.1: http://darcs.net/Releases/2.10#whats-new-in-2.10.1 thanks Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] new diff algorithm
Hi Henning, thanks for the kind comment! Indeed the new diff algorithm is called patience diff and is different and arguably more natural than the traditional myers diff. In Darcs 2.10 you can compare both diff outputs in commands like whatsnew or record by passing the flag --myers to get the old behaviour. Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] hcar 2015-05 draft
Nice! In further reading you could add this link: http://darcs.net/Releases/2.10 instead of the GSoC links. ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] darcs 2.10.0 release
Hi all, The darcs team is pleased to announce the release of darcs 2.10.0. # Downloading # The easiest way to install darcs 2.10.0 from source is by first installing the Haskell Platform (http://www.haskell.org/platform). If you have installed the Haskell Platform or cabal-install, you can install this release by doing: $ cabal update $ cabal install darcs-2.10.0 Alternatively, you can download the tarball from http://darcs.net/releases/darcs-2.10.0.tar.gz and build it by hand as explained in the README file. The 2.10 branch is also available as a darcs repository from http://darcs.net/releases/branch-2.10 # Feedback # If you have an issue with darcs 2.10.0, you can report it via the web on http://bugs.darcs.net/ . You can also report bugs by email to bugs at darcs.net, or come to #darcs on irc.freenode.net. # What's new since darcs 2.8.5 # ## New features ## - darcs rebase: enable deep amending of history (Ganesh Sittampalam) - darcs pull --reorder: keep local-only patches on top of mainstream patches (Ale Gadea, Ganesh Sittampalam) - darcs dist --zip: generate a zip archive from a repository (Guillaume Hoffmann) - patch bundle contexts are minimized by default. Enables bundles to be applied to more repositories. (Guillaume Hoffmann) - darcs convert export/import for conversion to/from VCSes supporting the fast-export protocol (Petr Rockai, Owen Stephens, Guillaume Hoffmann, Lele Gaifax, Ben Franksen) - darcs test --backoff: exponential backoff test strategy, faster than bisect on big repositories (Michael Hendricks) - work normally on sshfs-mounted repositories (Nathaniel Filardo) - automatic detection of file/directory moves, and of token replaces (Jose Neder) - patience diff algorithm by default (Jose Neder) - interactive mode for whatsnew (Dan Frumin) - tag --ask-deps to create tags that may not include some patches (Ganesh Sittampalam) ## User Interface ## - add a last question after all patches have been selected to confirm the whole selection (Florent Becker) - command names: - clone is the new name of get and put - log is the new name of changes - amend is the new name of amend-record - show output of log into a pager by default (Guillaume Hoffmann) - the output of log is more similar to git's: - show patch hash in UI (hash of the patch's metadata) - put author and date on separate lines (Guillaume Hoffmann) - enable to match on patch hash prefix with -h and --hash (Guillaume Hoffmann, Gian Piero Carrubba) - better messages: - better error messages for http and ssh errors (Ernesto Rodriguez) - init, add, remove, move and replace print confirmation messages (Guillaume Hoffmann) - rollback only happens in the working copy (Florent Becker, Guillaume Hoffmann) - darcs send no longer tries to send a mail by default (Eric Kow) - when no patch name given, directly invoke text editor (Jose Neder, Guillaume Hoffmann) - use nano as default text editor instead of vi (Guillaume Hoffmann) - keep log files for patch name and mail content in _darcs (Ale Gadea) - optimize and convert are now supercommands (Guillaume Hoffmann) - improve darcs help environment and darcs help markdown (Radoslav Dorcik, Guillaume Hoffmann) - warn about duplicate tags when creating a new one (Ale Gadea) - allow darcs mv into known, but deleted in working, file (Owen Stephens) - improve --not-in-remote, allowing multiple repos and use default (Owen Stephens) ## Performance ## - faster darcs diff (Petr Rockai) - faster log and annotate thanks to patch index data structure (BSRK Aditya, Benedikt Schmidt, Eric Kow, Guillaume Hoffmann, Ganesh Sittampalam) - faster push via ssh by using compression (Ben Franksen) - cloning to an ssh destination (formerly darcs put) is more efficient (Guillaume Hoffmann) - faster internal representation of patch hashes (Guillaume Hoffmann) - when cloning from http, use packs in a more predictable way (Guillaume Hoffmann) - store global cache in bucketed format (Marcio Diaz) ## Developer-related ## - require and support GHC 7.4 to 7.10 (Ganesh Sittampalam) - replace type witness CPP macros with plain Haskell (Eric Kow) - hashed-storage is bundled into darcs (Ganesh Sittampalam) - replace C SHA256 bindings with external libraries (Ganesh Sittampalam) - move the bits of the datetime package we need into Darcs.Util.DateTime (Ganesh Sittampalam) - build Darcs once rather than thrice. (Eric Kow) - remove home page and manual from darcs' repository (Guillaume Hoffmann) - run tests through cabal test (Ryan Desfosses) - run fewer darcs-1 related tests in testsuite (Ganesh Sittampalam) - Use custom replHook to fix cabal repl (Owen Stephens) - darcs.cabal: make Haskell2010 the default-language for all stanzas (Ben Franksen) - always compile with mmap support (Ganesh Sittampalam) - new options subsystem (Ben Franksen) - various cleanups, code restructurations and refactoring, haddocks (Will Langstroth, Owen Stephens, Florent Becker
Re: [darcs-users] Conflicts handling UI: GSoC proposal
The proposal is also on the website (not sure if the previous link is publicly readable): http://darcs.net/GSoC/2015-Conflicts-Handling-and-UI ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] [darcs-devel] release 2.10 process
An update on the darcs 2.10 release: * we are close to it, the biggest bugs have been fixed. * there are still unresolved bugs that are linked from the release page, but the only blocker is 2438, which already has a patch that I will accept friday if there is no objection ( http://bugs.darcs.net/patch1298 ) * I'm going to skip the release candidate stage and release 2.10.0, probably at the beginning of next week You can already see the enormous amount of work done since Darcs 2.8 at http://darcs.net/Releases/2.10 thanks Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] Darcs News #110
# News and discussions 1. The Darcs 2.10 release is near! Please test the release branch and tell us if you find a bug. - http://darcs.net/Releases/2.10 - http://lists.osuosl.org/pipermail/darcs-users/2015-March/027105.html 2. Joachin Breitner has shut down his darcswatch service after 7 years of activity: - http://lists.osuosl.org/pipermail/darcs-users/2015-February/027102.html - http://lists.osuosl.org/pipermail/darcs-users/2015-February/027104.html - http://www.joachim-breitner.de/blog/672-DarcsWatch_End-Of-Life%E2%80%99d # Issues resolved (11) issue822 Ernesto Rodriguez ~ - Generalized the IO Type for better error messages and exception handling - http://bugs.darcs.net/issue822 issue2260 Ganesh Sittampalam ~ - skip internal patches when counting - http://bugs.darcs.net/issue2260 issue2385 Guillaume Hoffmann ~ - invoke pager without temporary file - http://bugs.darcs.net/issue2385 issue2410 Guillaume Hoffmann ~ - detect replaces even with tokens of different lengths - http://bugs.darcs.net/issue2410 issue2411 Guillaume Hoffmann ~ - ignore swap moves with --look-for-moves - http://bugs.darcs.net/issue2411 issue2414 Guillaume Hoffmann ~ - use parseFlags instead of toMatchFlags where needed - http://bugs.darcs.net/issue2414 issue2418 Guillaume Hoffmann ~ - add and check on-disk patch index version - http://bugs.darcs.net/issue2418 issue2422 Ganesh Sittampalam ~ - drop unneeded LambdaCase extension - http://bugs.darcs.net/issue2422 issue2427 Ben Franksen ~ - start conversion from intermediate tree state - http://bugs.darcs.net/issue2427 issue2431 Ben Franksen ~ - rollback Control.Monad.Catch generalizations - http://bugs.darcs.net/issue2431 issue2432 Ganesh Sittampalam ~ - use the merged version of the local patches - http://bugs.darcs.net/issue2432 issue2437 Guillaume Hoffmann ~ - fix cloning to ssh by forgetting source repo later - http://bugs.darcs.net/issue2437 # Patches applied (111) 2015-03-02 Ganesh Sittampalam ~ - resolve issue2432: use the merged version of the local patches - fix warning 2015-02-22 Guillaume Hoffmann ~ - resolve issue2437: fix cloning to ssh by forgetting source repo later - bump version to 2.11.0 - bump version to 2.10.0 2015-02-10 Ganesh Sittampalam ~ - -D_REENTRANT shouldn't be conditional on -frtsopts 2015-02-27 Guillaume Hoffmann ~ - license DateTime module as BSD3, with original author approval 2015-02-25 Ganesh Sittampalam ~ - move the bits of the datetime package we need into a Darcs.Util.DateTime module 2015-02-26 Guillaume Hoffmann ~ - NEWS update for Darcs 2.8.x releases 2015-02-21 Ben Franksen ~ - resolve issue2431: rollback Control.Monad.Catch generalizations - cleanup: removed old disabled code for isInteractive - re-implemented getOutput in terms of the option spec - cleanup: renamed applyas to applyAs - purged RemoteApply of DarcsFlag remains - fix: moved import of applyAs from Darcs.UI.RemoteApply to Darcs.UI.Flags - cleanup: renamed PatchIndexOption to WithPatchIndex - cleanup: Repository.Format and .Internal haddocks and variable names - fixed type of identifyRepositoryFor according to TODO in comment - cleanup: import anchoredRoot instead of internal representation 2014-12-13 Ganesh Sittampalam ~ - tweak takeHeadRebase docs/message a bit - support GHC 7.10/base 4.8 2015-01-26 Ben Franksen ~ - fix: use getExecutablePath only if ghc version = 7.6 - resolved issue2333: use getExecutablePath instead of getProgName 2015-02-10 Ganesh Sittampalam ~ - skip issue2333 test on GHC 7.4 2015-01-25 Ben Franksen ~ - accept issue2333: Error message when pushing and darcs not in path - cleanup: tentativelyReplacePatches is only used internally - cleanup: slightly streamlined doRecord - cleanup: indentation of commandControlList - fixed completion for help command - fixed failing fromJust in look-for-replaces implementation - adding -K option to less fixes leaking last line after Ctrl-C 2015-02-12 Guillaume Hoffmann ~ - resolve issue2385: invoke pager without temporary file 2015-02-19 Ganesh Sittampalam ~ - resolve issue2260: skip internal patches when counting 2015-02-18 Guillaume Hoffmann ~ - remove in-depth help of repo format error, redundant with scp's errors - resolve issue2410: detect replaces even with tokens of different lengths - remove last dependency on extensible-exceptions - remove always true condition ghc = 6.8 in cabal file - no longer use extensible-exceptions since we require ghc 7.4 - bump dependencies lower bounds implied by requiring ghc 7.4 2015-02-10 Ben Franksen ~ - cleanup: restructured haddocks in the options core module, simplified parseFlags
[darcs-users] summer of code 2015 ideas: wreq / darcsden
Dear darcs'ers, this year's Summer of Code program starts son: by end of March, student applications should be submitted to Google. We are probably going to work again with students that have not contributed to darcs before. Since two students in my university are interested about it, I'd like to hear your comments about the following two project ideas I thought of. 1. HTTP system overhaul, a.k.a. switch to wreq and see what happens. This would involve having wreq (http://www.serpentine.com/wreq/) as default download system, while leaving the current libcurl and HTTP code for benchmarking purposes. The benefits would be: * no longer requiring separate compilation/installation of libcurl * https support under windows (somehow we can't have libcurl under windows?) * access to repositories behind http authentication (and probably other benefits of wreq) Deliverables (apart from the code itself): * HTTP benchmarks (wreq vs libcurl vs HTTP) * testing that pipelining actually works * testing under windows / linux 2. Work towards Darcsden as a local UI and other improvements * plain files backend (vs current CouchDB) * other stuff to help Darcsden be a local UI (without actually involving any UI work)? any idea? * unauthenticated patch submission via darcs send and http Apart from opinions about these project ideas, if someone thinks there are more worthwile projects to do, please tell. Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] [darcs-devel] release 2.10 process
Hi Ben (and others), sorry for being missing-in-action for so long, The combined effect of end-of-year celebrations and summer holidays (here in the south hemisphere) removed me from darcs development for a long time. Next week I'll be able to come back to working on it. I think we can aim at finishing darcs 2.10 by end of February. In november and december Ganesh and I worked on patch index memory use, which finally became acceptable. Fortunately we don't have a big divergence between screened, reviewed and branch-2.10. I saw there was work on encoding, and on the flag system, which are topics for which I'm not an expert. Can you see if you can (self-)accept patches related to these topics? Here is the list of open bugs for 2.10: http://tinyurl.com/nay7jq4 Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] Darcs News #109
# News and discussions 1. We are in the feature freeze period of darcs 2.10: - http://lists.osuosl.org/pipermail/darcs-users/2014-November/027056.html 2. Our two Summer of Code projects ended up two months ago. Marcio and Ale's code will be part of the upcoming new stable version of darcs. In case you missed them, here are the latest posts of Marcio for his project: - http://marcioodiaz.blogspot.com.ar/2014/07/gsoc-progress-report-3-bucketed-global_23.html - http://marcioodiaz.blogspot.com.ar/2014/07/gsoc-progress-report-4-garbage.html - http://marcioodiaz.blogspot.com.ar/2014/07/gsoc-progress-report-5-starting.html Ale's posts: - http://alegdarcs.blogspot.com.ar/2014/07/month-of-june.html - http://alegdarcs.blogspot.com.ar/2014/07/some-week-14-19-july.html - http://alegdarcs.blogspot.com.ar/2014/07/other-week-21-26-july.html - http://alegdarcs.blogspot.com.ar/2014/08/last-few-weeks.html # Issues resolved (7) issue1514 Guillaume Hoffmann ~ - send --minimize-context flag for send - http://bugs.darcs.net/issue1514 issue1624 Marcio Diaz ~ - bucketed cache. - http://bugs.darcs.net/issue1624 issue2153 Andreas Brandt ~ - allow skipping backwards through depended-upon patches - http://bugs.darcs.net/issue2153 issue2249 Mateusz Lenik ~ - Rename isFile to isValidLocalPath and WorkRepoURL to WorkRepoPossibleURL - http://bugs.darcs.net/issue2249 issue2380 Owen Stephens ~ - allow darcs mv into known, but deleted in working, file - http://bugs.darcs.net/issue2380 issue2403 Ganesh Sittampalam ~ - need to avoid moving the rebase patch to the end - http://bugs.darcs.net/issue2403 issue2409 Ganesh Sittampalam ~ - implement darcs rebase apply - http://bugs.darcs.net/issue2409 # Patches applied (118) 2014-11-07 Guillaume Hoffmann ~ - directly pass around SHA1 of patches instead of string representation 2014-11-05 Ganesh Sittampalam ~ - fix warnings - update messages mentioning darcs optimize --patch-index - make the help message for --ask-deps generic - basic test of tag --ask-deps - Disallow skip all option in interactive selection for tag --ask-deps - Initial implementation of --ask-deps flag to darcs tag - rename the confusing concept of 'Tag' in Darcs.Patch.Choices to 'Label' - push the WhichChanges choice into the PatchSelectionContext 2014-11-05 Guillaume Hoffmann ~ - correctly take into account --[no-]edit-description - revert send default to --edit-description - put again as verbose-only the patches pack fail message on cloning 2014-11-04 Ben Franksen ~ - integrate new options subsystem 2014-10-27 Ganesh Sittampalam ~ - Make the rebase changes output more user-friendly - resolve conflicts - add a unit test for RebaseChange - resolve conflicts - change/add various Show instances to ones that produce Haskell code - stop using custom Show instance on PatchInfo - rebase changes: delegate listConflictedFiles etc instead of using default - abstract code for treating RebaseChange as a merge - resolve conflicts - initial version of 'rebase changes' command - introduce a new type class for patch matching - resolve conflict (getChangesInfo flag changes and renaming) - make getChangesInfo take specific flags only - resolve conflicts (getChangesInfo renaming and refactoring) - resolve conflicts (addition of diff algorithm and getChangesInfo refactoring) - make getChangesInfo take a PatchFilter instead of a Repository - fix warning - reduce dependencies for Named/PatchInfoAnd Patchy instances - drop unnecessary UndecidableInstances - Work around haskell-src-exts (and hence hlint) parse errors - resolve issue2409: implement darcs rebase apply - switch applyCmd to use the PatchApplier abstraction - reuse the standard pullCmd for rebase - generalise applyPatchesForRebase along the same lines as applyPatches - bundle up checking for patch index and using it 2014-10-23 Guillaume Hoffmann ~ - add --no-minimize flag to fix broken tests - minimize bundle contexts by default, allow ctrl-c or --no-minimize 2014-10-16 Ganesh Sittampalam ~ - pattern-match against Sealed rather than using unsafeUnseal 2014-10-15 Guillaume Hoffmann ~ - --minimize for obliterate -O - resolve issue1514: send --minimize-context flag for send 2014-10-21 Ganesh Sittampalam ~ - resolve issue2403: need to avoid moving the rebase patch to the end - Share applyPatches code between pull and apply - clarify naming of applyPatches functions - resolve conflict in improved 'darcs replace' message - improve message from force-replace 2014-06-29 Ben Franksen ~ - replaced duplicate DiffAlgorithm in Darcs.Repository.Flags with re-export - Darcs.Repository.Flags
Re: [darcs-users] Using hash(es) for selecting one or more patches
Please create a bug ticket and assign it to the 2.10 release :) ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] incoming darcs 2.10 feature freeze
Feature freeze has begun. The code for the 2.10 release lives at: http://darcs.net/releases/branch-2.10/ http://darcs.net/releases/branch-2.10/branch-2.10.zip The bugs that should be fixed for the release can be found at: http://tinyurl.com/lusjd38 This list of bugs still needs some triaging, and the 'feature' category should now be ignored. The todo/what's new page for the release is http://darcs.net/Releases/2.10 Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] skeptical review requested: darcs tag --ask-deps
The absence of 'd' surprised me, but I guess the idea is that you want a tag to tag 'almost everything' instead of 'almost nothing' in a repository. Otherwise you create a patch with --ask-deps. On a related note, indeed darcs amend [--unrecord] --ask-deps does not work on tags, so this is a missing feature. I think it's good as it is now. Probably the help string of the flag --ask-deps should say someting like manually select dependencies. ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] hcar 2014 november draft
It is fine as it is. Thanks Eric! ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] memory consuption of patch index in darcs 2.10
Hi, the patch index data structure will be present in darcs 2.10. It is currently enabled by default in the development version of darcs (since now 2 years). We still have a problematic issue with it, that is, when cloning big repositories, patch index creation consumes lots of memory. In some cases (on my computer, when darcs is built without optimizations), it ends up with a stack overflow error. See http://bugs.darcs.net/issue2405 for more details. If someone is interested in investigating this issue please look at: * http://darcs.net/Using/PatchIndex * http://darcs.net/Internals/PatchIndex * the function [Darcs.Repository.PatchIndex.createOrUpdatePatchIndexDisk](http://hub.darcs.net/darcs/darcs-screened/browse/src/Darcs/Repository/PatchIndex.hs#445) It would be nice to fix this by the 2.10 release, otherwise I would be in favor of disabling it by default. Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] incoming darcs 2.10 feature freeze
Hi, not before next november 3th, I'm kicking off the release process of darcs 2.10 ( http://darcs.net/Development/ReleaseManagement ). That is, I will clone our reviewed repository into a release-2.10 repository, and from then on the only stuff that will go in will be bugfixes, optimizations and helpstrings. A description about what's already in 2.10 (new features, etc.) can be found at http://darcs.net/Releases/2.10 Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] Using hash(es) for selecting one or more patches
The patch is now in screened (ie, the repository http://darcs.net). ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] Using hash(es) for selecting one or more patches
Then I think it is worth trying using -h for hash matching in 2.10. I'll send a followup patch to the bundle http://bugs.darcs.net/patch1177 soon. ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] Using hash(es) for selecting one or more patches
Hi Gian Piero now that `log` shows the hash of the patches, I would like to use it for selecting patches as `log (or whatever) -p` is not much handy where there are similar- or same-named patches. On the other hand, typing `--match 'hash` is boring, so I've added a `-H/--hash`[0] option that aliases to `--match 'hash ...'`. I think it's a good idea. I wouldn't even mind using -h (currently used as --help). Some programs use it as a --help alias (svn, hg), others don't (git, ghc). Then I've changed idea and instead thought that I would prefer to continue using `-p` and darcs should discriminate if I've provided a regex or a hash. So I've modified `-p` (and the related `--from-patch` and `--to-patch`) in order to consider its argument as a hash if it's 40 chars long and only composed by hex digits. advantages: - much shorter patch I'm not sure I understand. You mean shorter flag? - no options inflating disadvantages: 1. no hash prefix matches: too many chances for false positives. Yeah I would also make this choice. 2. lack of correctness if your regex happens to be a 40 digits long hex. In this case you would have to resort to `--match 'name ...'` Yes that's a concern. If we had (or will have in the future) a short-id like other VCSs, we could use both full and short versions for alleviate 1, but this would OTOH aggravate 2. While I consider the chances for 2. pretty limited, the drawbacks seem serious: user's surprise, breakage of sw that automatically names patches using hashes, possible kittens injuries, ... Indeed. I wonder if people out there use hashes as patch names? Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] Whatsnew on a rolled back repo
The revert command creates a bundle in _darcs/patches/revert , you way find the information you need in that file. 2014-08-17 6:26 GMT-03:00 Gian Piero Carrubba gpi...@rm-rf.it: Use case: I've a repo with patches A and B that are mutually exclusive. They aren't conflicting, but both define a same-named function, so the sw won't compile if both are applied. The simple solution is to rollback the undesired one before compiling, then revert the repo afterwards. Now I've discovered that last time I've forgotten to do the revert step. If I do a revert now, I'll lose any change I could have done in the repo while in the rolled-back status, so I need a way for displaying the changes in the working dir other than the ones generated by the rollback command. Sorry, there is no simple way of tracking these changes apart from other, manual, changes you may have done in the working copy. You may clean your working copy with the default, interactive revert command. Another option would be to clone your repository R1 into another one R2, run rollback of the same function in R2, record a patch P1, then copy the working copy of R1 into R2 and record a patch P2. If P1 and P2 commute, you can pull P1 it back into R1 (after reverting everything there). Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] planning a 2.8.5
Here's a patch to support network 2.6. This only affects building when the HTTP library is used. Works with: cabal install -fhttp# to use network = 2.6 cabal install -fhttp -f-network-uri # to use network 2.6 Guillaume support-network-2_6.dpatch Description: Binary data ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] planning a 2.8.5
Here's a patch to enable matching on the short patch hash, so that darcs 2.8.5 be more future-proof with regards to darcs 2.10. enable-to-match-on-short-patch-hash-_future_proofing-wrt-darcs-2_10_.dpatch Description: Binary data ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] planning a 2.8.5
Looks sufficient to me. ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] Darcs News #108
# News and discussions 1. We have a few updates from the Google Summer of Code projects. Alejandro Gadea about history reordering: - http://alegdarcs.blogspot.com.ar/2014/05/first-week-19-23-may.html - http://alegdarcs.blogspot.com.ar/2014/06/second-week-26-30-may.html - http://alegdarcs.blogspot.com.ar/2014/06/third-week-02-06-june.html 2. Marcio Diaz about the cache system: - http://marcioodiaz.blogspot.com.ar/2014/06/gsoc-progress-report-2-bucketed-global.html 3. Incremental fast-export is now provided to ease maintenance of git mirrors: - http://hub.darcs.net/darcs/darcs-screened/patch/20140609190214-5ef8f # Issues resolved (8) issue2244 Ale Gadea ~ - darcs tag should warn about duplicate tags - http://bugs.darcs.net/issue2244 issue2314 Benjamin Franksen ~ - output-auto-name in defaults file - http://bugs.darcs.net/issue2314 issue2361 Ale Gadea ~ - optimize --reorder runs forever with one repository - http://bugs.darcs.net/issue2361 issue2364 Sergei Trofimovich ~ - fix file corruption on double fetch - http://bugs.darcs.net/issue2364 issue2364 Sergei Trofimovich ~ - don't break list of 'bad sources' - http://bugs.darcs.net/issue2364 issue2388 Owen Stephens ~ - check if inventories dir has been created - http://bugs.darcs.net/issue2388 issue2394 Guillaume Hoffmann ~ - make optimize a supercommand - http://bugs.darcs.net/issue2394 issue2396 Guillaume Hoffmann ~ - make convert a supercommand and enhance help strings - http://bugs.darcs.net/issue2396 # Patches applied (39) 2014-06-24 Guillaume Hoffmann ~ - update issue2388 test to optimize supercommand 2014-05-11 Owen Stephens ~ - Resolve issue2388: check if inventories dir has been created - Accept issue 2388 2014-05-30 Ganesh Sittampalam ~ - indentation fix for Windows-only module 2014-05-11 Benjamin Franksen ~ - fixed a typo in a comment in Darcs.Util.Diff.Patience - Allow options with path arguments to be specified in defaults file - fixed cut-n-paste error in haddock comment - resolve issue2314: output-auto-name in defaults file 2014-05-11 Owen Stephens ~ - Accept issue2386 2014-06-12 Guillaume Hoffmann ~ - remove patch index flags from rollback command - resolve issue2396: make convert a supercommand and enhance help strings - factorize boilerplate of optimize subcommands - resolve issue2394: make optimize a supercommand - adapt testsuite to new optimize supercommand 2014-05-11 Benjamin Franksen ~ - make optimize command respect --quiet by using putInfo - darcs.cabal: make Haskell2010 the default-language for all stanzas 2014-06-18 Guillaume Hoffmann ~ - explain commandProgramName 2014-05-07 Benjamin Franksen ~ - fixed missing option for author in rebase-nochanges.sh test - added _test_playground to boring file - added cabal sandbox generated stuff to boringfile - avoid a syntax error with haddock-2.13.2 2014-04-29 Sergei Trofimovich ~ - resolve issue2364: fix file corruption on double fetch 2014-04-30 Owen Stephens ~ - Use DeriveFunctor instead of manual instance for PatchMod 2014-06-09 Guillaume Hoffmann ~ - marksfile support for convert --export 2014-06-11 Ale Gadea ~ - Documentation of function Darcs.Repository.Internal.misplacedPatches . - Documentation for Darcs.Patch.Witnesses.Sealed module. - Documentation for Darcs.Patch.Witnesses.Ordered module. 2014-06-03 Ganesh Sittampalam ~ - conditionalise replHook using Template Haskell 2014-06-05 Ale Gadea ~ - Resolve Issue2361: optimize --reorder runs forever with one repository 2014-05-16 Guillaume Hoffmann ~ - implement doFastZip to create zip archive from pristine tree 2014-05-29 Ganesh Sittampalam ~ - re-advertise GHC 7.8 support - clean out some obsolete conditionalisation - bump version to 2.9.9 2014-05-19 Guillaume Hoffmann ~ - rm latex2html file 2014-05-13 Sergei Trofimovich ~ - resolve issue2364: don't break list of 'bad sources' 2014-04-27 Owen Stephens ~ - Accept issue2382: darcs is confused if a dir is moved inplace of a file - Accept issue2383 - Accept issue2380: darcs wont rename a file to the name of a deleted file 2014-05-07 Ale Gadea ~ - Resolve Issue2244: darcs tag should warn about duplicate tags ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] Darcs News #107
# News and discussions 1. Darcs has received two grants from the Google Summer of Code program, as part of the umbrella organization Haskell.org. Alejandro Gadea will work on history reordering: - http://alegdarcs.blogspot.com.ar/2014/05/google-summer-of-code-2014-darcs.html 2. Marcio Diaz will work on the cache system: - http://marcioodiaz.blogspot.com.ar/2014/04/gsoc-project-accepted.html - http://marcioodiaz.blogspot.com.ar/2014/04/gsoc-progress-report-1-complete.html 3. Repository cloning to remote ssh hosts has been present for years as `darcs put`. This feature has now a more efficient implementation: - http://hub.darcs.net/darcs/darcs-reviewed/patch/20140425060647-5ef8f # Issues resolved (11) issue851 Dan Frumin ~ - interactive mode for whatsnew - http://bugs.darcs.net/issue851 issue1066 Guillaume Hoffmann ~ - clone to ssh URL by locally cloning then copying by scp - http://bugs.darcs.net/issue1066 issue1268 Guillaume Hoffmann ~ - enable to write darcs init x - http://bugs.darcs.net/issue1268 issue1416 Ale Gadea ~ - put log files in tempdir instead of in working dir. - http://bugs.darcs.net/issue1416 issue1987 Marcio Diaz ~ - Garbage collection for inventories and patches. - http://bugs.darcs.net/issue1987 issue2263 Ale Gadea ~ - Option --set-scripts-executable is not properly documented - http://bugs.darcs.net/issue2263 issue2345 Dan Frumin ~ - solution using cabal's checkForeignDeps - http://bugs.darcs.net/issue2345 issue2357 Dan Frumin ~ - switching to regex-compat-tdfa for unicode support - http://bugs.darcs.net/issue2357 issue2365 Guillaume Hoffmann ~ - correctly copy pristine in no-working-dir clones - http://bugs.darcs.net/issue2365 issue2367 Guillaume Hoffmann ~ - rename amend-record to amend, make --unrecord more visible - http://bugs.darcs.net/issue2367 issue2379 Guillaume Hoffmann ~ - only use packs to copy pristine when up-to-date - http://bugs.darcs.net/issue2379 # Patches applied (41) 2014-05-03 Owen Stephens ~ - Use custom replHook to fix cabal repl - Use DeriveFunctor instead of manual instance for PatchMod 2014-04-25 Guillaume Hoffmann ~ - update packs tests to new strings - resolve issue1268: enable to write darcs init x - rename get to clone - remove Put since Get can clone to ssh destination faster - resolve issue1066: clone to ssh URL by locally cloning then copying by scp - do not tolerate ctrl+c when --complete is passed - do not print message twice when patches pack grabbing fails - create inventories subdir at darcs init 2014-04-24 Ganesh Sittampalam ~ - TAG 2.9.9 2014-04-22 Guillaume Hoffmann ~ - resolve issue2365: correctly copy pristine in no-working-dir clones - rename copyRepo to copyHashedInventory, separate copySources - only print once repository renaming message when cloning - maybeIdentifyRepository: report missing _darcs directory right away - no longer make put autocomplete on known repos - rename setDefaultrepo to addRepoSource and haddock it - resolve issue2379: only use packs to copy pristine when up-to-date 2014-02-08 Dan Frumin ~ - A shell test for `whatsnew --interactive` - resolve issue851: interactive mode for whatsnew - Cleaning up the headers in WhatsNew and SelectChanges 2014-04-23 Ganesh Sittampalam ~ - switch hashed-storage-test to be a proper test harness - dumb merge of hashed-storage.cabal etc into darcs.cabal - drop NoMonomorphismRestriction from hashed-storage - conditionally use local copy of Data.Map.Strict in Darcs.Repository.Util 2014-02-14 Dan Frumin ~ - resolve issue2357: switching to regex-compat-tdfa for unicode support - resolve issue2345: solution using cabal's checkForeignDeps 2014-04-22 Owen Stephens ~ - Add a test for all combinations of path status for darcs move 2014-04-19 Ganesh Sittampalam ~ - don't advertise GHC 7.8 support until http://bugs.darcs.net/issue2364 is fixed 2014-04-10 Guillaume Hoffmann ~ - resolve issue2367: rename amend-record to amend, make --unrecord more visible - Accept issue2365: whatsnew fails in repos made w get --no-working-dir 2014-04-09 Marcio Diaz ~ - resolve issue1987: Garbage collection for inventories and patches. - Accept issue1987: regression tests for garbage collection for 2014-04-08 Guillaume Hoffmann ~ - fix warning in Record 2014-04-08 Ale Gadea ~ - Resolve Issue1416: put log files in tempdir instead of in working dir. 2013-10-27 Guillaume Hoffmann ~ - TAG 2.9.8 - bump version to 2.9.8 2013-09-06 Petr Rockai ~ - Fix a bug in MIME encoding of bundles. 2014-03-17 Guillaume Hoffmann ~ - eliminate withRepoReadLock obsolete since old-fashioned deprecation - polish help string on get --set-strings-executable
[darcs-users] Darcs News #106
# News and discussions 1. Darcs is participating once again to the Google Summer of Code, through the umbrella organization Haskell.org. Deadline for student application is Friday 21st: - http://darcs.net/GSoC - https://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2014/help_page 2. It is now possible to donate stock to darcs through the Software Freedom Conservancy organization. Donations by Paypal, Flattr, checks and wire transfer are still possible: - http://lists.osuosl.org/pipermail/darcs-users/2013-December/026977.html - http://darcs.net/Donations 3. Dan Licata wrote a presentation about Darcs as a higher inductive type: - http://lists.osuosl.org/pipermail/darcs-users/2014-January/026985.html 4. Darcs now directly provides import and export commands with Git. This code was adapted from Petr Rockai's darcs-fastconvert, with some changes by Owen Stephen from his Summer of Code project darcs-bridge: - http://hub.darcs.net/darcs/darcs-screened/patch/20140125154537-5ef8f # Issues resolved (6) issue642 Jose Luis Neder ~ - Automatic detection of file renames - http://bugs.darcs.net/issue642 issue2209 Jose Luis Neder ~ - Automatically detect replace - http://bugs.darcs.net/issue2209 issue2319 Guillaume Hoffmann ~ - make changes non-interactive if fed to a pipe - http://bugs.darcs.net/issue2319 issue2332 Guillaume Hoffmann ~ - ignore case of characters in prompt - http://bugs.darcs.net/issue2332 issue2335 Guillaume Hoffmann ~ - one liner when adding tracked files if not verbose - http://bugs.darcs.net/issue2335 issue2348 Ryan ~ - switch to cabal's test framework - http://bugs.darcs.net/issue2348 # Patches applied (34) 2014-03-02 Guillaume Hoffmann ~ - pandoc-ize README and remove mention of old flags and warnings - resolve issue2332: ignore case of characters in prompt 2014-01-26 Dan Frumin ~ - Making sure darcs builds on OSX Mavericks 2014-02-08 Ganesh Sittampalam ~ - hashed-storage: GHC 7.8 build fix - support GHC 7.8 and various assorted other version bumps - drop support for GHC 7.0/7.2 - get rid of now redundant conditionalisation - remove accidentally added file - fix hashed-storage build on Windows - we need utf8-string on Windows too now for the fast-export/import code - bump cryptohash dependency 2014-01-25 Guillaume Hoffmann ~ - Implement convert --export and --import for git conversion 2014-01-10 Jose Luis Neder ~ - resolve issue2209: Automatically detect replace 2014-01-08 Guillaume Hoffmann ~ - remove useless check of xml-output in get and convert - add hashed-storage 0.5.11 2013-09-15 Jose Luis Neder ~ - resolve issue642: Automatic detection of file renames - Show fileid info with show index 2013-11-28 Ryan ~ - resolve issue2348: switch to cabal's test framework 2013-11-27 Guillaume Hoffmann ~ - fix bug when global prefs dir does not exist and try to save author name 2013-11-26 Ganesh Sittampalam ~ - improve help text - need to use ByteString to read tests on unix - fix warnings - add a TODO comment - add pragmas to shell tests to allow for the test to specify configurations - remove explicit choice of Myers diff from test - add command-line options to control global test options 2013-10-11 Guillaume Hoffmann ~ - resolve issue2335: one liner when adding tracked files if not verbose - announce added files with existing infrastructure - rename changes command to log, keep changes as alias - output darcs changes to a pager if more than 20 lines big - Make changes non-interactive by default again 2013-06-14 Guillaume Hoffmann ~ - make changes non-interactive when given flags --count or --xml-output 2013-05-09 Guillaume Hoffmann ~ - fix issue2270 test since piped darcs changes is now never interactive - resolve issue2319: make changes non-interactive if fed to a pipe ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] Google Summer of Code 2014: ideas wanted
Haskell.org has been selected as mentoring organization by Google: https://www.google-melange.com/gsoc/org/list/public/google/gsoc2014 Next deadline, March 10th for the beginning of the student application period (ends March 21st). ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] Google Summer of Code 2014: ideas wanted
Hi, this year's google summer of code starts quite early. Student application deadline is March 21st and Internship happens between May 19th and August 18th. But most importantly now, organization application deadline is Feb 14th, that is, next Friday. Darcs will probably be part of the haskell.org organization like every year, but it's always good to have our own Ideas page up to date and as full as possible (we may apply ourselves anyway). So you have ideas for a project, please edit http://darcs.net/GSoC , or if you don't have a wiki account, just shoot here and I'll add it to the page. Also if you're a student and want to participate, please talk to us here or on IRC. Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] providing one-time fast-export in darcs
I've sent http://bugs.darcs.net/patch and suggest the discussion continues on darcs-devel / the patch tracker, if that's okay? ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] providing one-time fast-export in darcs
With regards to code duplication/divergence: I am proposing a minimal feature that would work for most cases. That is, small size of code, and without trying to be too clever (eg, the conflicts issue). So yes, there would be some duplication, something like 150 lines. darcs-bridge would still be useful for more serious cases (incremental and back-and-forth conversions). Export is the easiest direction of both because 1) it's read-only 2) a darcs repository history is simpler than a git or mercurial repository history (a darcs history is linear, git/hg can have branches and more than one head). This is what makes the import direction harder to get right. So my main concern is that a subpar implementation import may not make sense at all. What do you think? I have limited experience with git branches and don't know how darcs-fastimport treats them. And yes, if really we want both export and import, then we could think about using the main command convert to store them (and reorganize it). Otherwise if we go for export only, `darcs log` seems more appropriate. ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] providing one-time fast-export in darcs
Hi, I'd like to suggest that darcs should provide built-in, one-time fast-export output. Let me explain why we would want this, and why only the export direction: - narrative for darcs 2.10: a built-in fast-export feature fits in a narrative that presents darcs as a system that people can try knowing they are free to switch to another tool without much work. I hope that it would lower the resistance to trying it. - maintainability: every now and then people pop up on IRC asking for the code of darcs-bridge, or saying that it does not build. (Granted, this happens with low frequency). With darcs providing natively a fast-export output we fix this situation for the export direction. - implementation easiness: we already have a couple of implementations ([1], [2]). After all fast-export without marks support is just a fancy `darcs log -v`. On the other hand, fast-import is much more complex (to begin with, it is not read-only) and still an open problem, AFAIK. I'm not sure if the best way to provide this feature would be `darcs log --fast-export`, or a new command like `darcs fast-export`. The former would convey the idea that the output is for a one-time use only, without marks support, with no garantee of being the same if history if reordered, etc. But if we want to support incremental export, then it gets more complicated that a fancy `darcs log` output, and probably deserves a separate command. I'd be happy with a minimal but working export support, with more feature-rich export/import tool being separated from darcs. Code duplication between seems smelly, but I think we are not talking about much code (between 125 lines in Petr's fastconvert [1] which would be what we would use, and 600 lines in Owen's darcs-bridge which is more complicated [2]). Opinions? Guillaume [1] http://repos.mornfall.net/darcs-fastconvert/Export.hs [2] http://hub.darcs.net/owst/darcs-bridge-export-branch/browse/Export.hs ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] make `darcs changes` interactive by default?
It may be a bad idea to do things differently just out of spite, but IMO a good reason is enough to be different. Demanding absolute necessity raises the bar a bit too high IMHO. The abolute was probably too much, nevertheless if we agree on such a guideline, we can get out of overlong debates, while taking not-so-bad design-related decisions. And it feels comfortable to have some vision of how the project should go on, at times when there is not really any leadership happening. g. ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] darcs news #105
# News and discussions 1. This year's Google Summer of Code projects brought a lot of improvements to darcs and its ecosystem! - BSRK Aditya: Darcsden improvements: - http://joyful.com/blog/2013-09-26-darcsden-darcs-hub-gsoc-complete.html - http://bsrkaditya.blogspot.com.ar/2013/09/darcsden-gsoc-final-blog-post.html - José Neder: patience diff, file move detection, token replace detection: - http://lists.osuosl.org/pipermail/darcs-users/2013-October/026945.html - http://blog.jlneder.com.ar/search/label/darcs 2. Gian Piero Carrubba asked why adjacent hunks could not commute: - http://lists.osuosl.org/pipermail/darcs-users/2013-November/026958.html 3. We listed the changes that occurred between version 2.8.4 and the current development branch into a 2.10 release page: - http://darcs.net/Releases/2.10?revision=20131028184855-5ef8f-ba33870773ad9ee010a470ac8536b5c7ae331b50 # Issues resolved (8) issue346 Jose Luis Neder ~ - implement patience diff from bzr - http://bugs.darcs.net/issue346 issue1828 Guillaume Hoffmann ~ - file listing and working --dry-run for mark-conflicts - http://bugs.darcs.net/issue1828 issue2181 Guillaume Hoffmann ~ - put cache in $XDG_CACHE_HOME (~/.cache by default) - http://bugs.darcs.net/issue2181 issue2309 Owen Stephens ~ - annotate includes line numbers - http://bugs.darcs.net/issue2309 issue2313 Jose Luis Neder ~ - whatsnew -l: Stack space overflow - http://bugs.darcs.net/issue2313 issue2334 Guillaume Hoffmann ~ - fix win32 build removing file permission functions - http://bugs.darcs.net/issue2334 issue2343 Jose Luis Neder ~ - darcs amend-record does not record my change - http://bugs.darcs.net/issue2343 issue2347 Guillaume Hoffmann ~ - fix amend-record --prompt-long-comment - http://bugs.darcs.net/issue2347 # Patches applied (39) 2013-10-28 Guillaume Hoffmann ~ - record: no longer accept first commented line as patch name - resolve issue2347: fix amend-record --prompt-long-comment - refuse incorrect patch names (empty or starting with TAG) 2013-06-15 Jose Luis Neder ~ - resolve issue2313: whatsnew -l: Stack space overflow - tests for issue2313: whatsnew -l: Stack space overflow 2013-02-17 Mark Stosberg ~ - new failing test for issue2303 - illustrates a Patch Index diagnostic that can be improved. - failing test for issue2272: darcs rebase unsuspend should succeed despite unrecorded changes - issue2271: New (passing) test which confirms that darcs optimize --disable-patch-index will fail in the face of a permissions problem. 2013-08-20 BSRK Aditya ~ - Export getChangesInfo from Changes command module 2013-09-22 Jose Luis Neder ~ - Add better comments to the issue2343 test file - resolve issue2343: darcs amend-record does not record my change 2013-08-20 Ganesh Sittampalam ~ - Introduce a local copy of Data.Map.Strict from containers 0.5, - Weaken hashable dependency 2013-08-13 Guillaume Hoffmann ~ - put upper bound on hashable dependency 2013-07-30 Jose Luis Neder ~ - make darcs-test run tests with both diff algorithms - resolve issue346: implement patience diff from bzr - name change Lcs.hs - Diff/Myers.hs 2013-08-05 Guillaume Hoffmann ~ - resolve issue2334 fix win32 build removing file permission functions 2013-08-27 BSRK Aditya ~ - When using send command, post the patch if using http, - Update containers minimum version 2013-08-12 Guillaume Hoffmann ~ - remove import warning - put newline after darcs diff changelog output - change format of patch name file when a text editor is invoked - remove redundant case in Darcs.UI.Command.Record.getLog - update unrecord and obliterate help, mention -O flag 2013-07-18 Owen Stephens ~ - Fix a couple of warnings from annotate with line numbers patch - Resolve issue2309: annotate includes line numbers 2013-07-25 Guillaume Hoffmann ~ - fix test for issue1290 for when tests are run in parallel - announce moved files - make move patch explicit - announce removed files - announce added files - resolve issue2181: put cache in $XDG_CACHE_HOME (~/.cache by default) - merge Darcs.Util.IO into Darcs.Util.File 2013-07-17 Owen Stephens ~ - Move chompNewline from Commands to Util/Text and rename to chompTrailingNewline 2013-07-04 Guillaume Hoffmann ~ - update help of mark-conflicts - resolve issue1828: file listing and working --dry-run for mark-conflicts 2013-03-18 Ganesh Sittampalam ~ - fix warnings introduced by issue1105 fix 2013-02-21 Florent Becker ~ - Fix issue1105 even in the presence of command-line optinos ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] make `darcs changes` interactive by default?
I like this, but making changes an alias for darcs log -i, thus avoiding disruption for old-time darcsers. I'm not sure about that, I believe all released versions changes has always been non-interactive by default (your patch that made it interactive only made its way into HEAD). ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] make `darcs changes` interactive by default?
I'm thinking more and more that darcs should have a behaviour similar to the most known VCS', unless there is some *absolute* necessity (by design or design principle) to do another way. The default expected use of changes (or log) is to show the history of a repository, and we cannot really fight this assumption. So I propose we go back to non-interactive by default. As of invoking the pager (a la git), good idea. We can indeed use the same code as `darcs help`. And to continue with the least surprise principle, I would go as far as proposing that changes should be called log (an alias already present in HEAD), and keep changes as an alias of log. (In the case it gets accepted, updating the documentation will be a to-do for darcs 2.10.) I don't want to close the debate right away; after sending patches for these 3 changes (which are almost ready) I will wait before even screening them (say until this week-end). ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] make `darcs changes` interactive by default?
Any thoughts about interactive changes by default? darcs screened has had it since a few months. In some cases it switches back to non-interactive (if fed to a pipe or given --count or --xml-output, see http://bugs.darcs.net/patch1071 ). Any regrets? Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] patience diff now in the reviewed branch
Short summary: darcs now uses a diff algorithm that generates more human hunks, especially when editing code written in languages with curly brackets. I've recently pushed José Neder's patches (based on code written by David Roundy) to the reviewed branch of darcs. See: * http://bugs.darcs.net/issue346 * http://bugs.darcs.net/patch1083 * http://blog.jlneder.com.ar/2013/07/patience-diff-algorithm-benefits-for.html It is now the default diff algorithm, affecting the commands whatsnew, record, amend, and a few others. It is still possible to use the previous diff algorithm by passing the --myers flag to these commands. Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] [darcs-devel] Mac OSX testers wanted: darcs unstable uses standard cache location
The point is to make all programs store their cache in the same directory, so that users can just delete it when they run out of space in their home directory. When it comes to configuration files, I guess the idea of storing them all in ~/.config is to 1) unclutter the home directory 2) make it easy to backup all user configuration file automatically. Thaks for your comment about ~/Library/Preferences, I didn't know. Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] Mac OSX testers wanted: darcs unstable uses standard cache location
Ok but can we assume that users never come back to old versions of darcs? If yes, then we can proceed to move everything: * detect if ~/.darcs exists * if yes, create ~/.config/darcs/, move everything under ~/.darcs/ except cache to ~/.config/darcs/ * if ~/.darcs/cache exists move ~/.darcs/cache/patches/* to ~/.cache/darcs/patches/* , same for inventories and pristine.hashed. * delete ~/.darcs (Adapt paths above to the Mac OSX case.) Otherwise if we are not sure, we could just leave .darcs there. We could make `darcs optimize` move the old cache to its new location, so that eventually future version of darcs only have to look at the new location. Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] Mac OSX testers wanted: darcs unstable uses standard cache location
Hi, I've just pushed to screened (ie http://darcs.net) a patch that makes darcs use a more standard cache location ( http://bugs.darcs.net/patch1080 ): This patch basically makes darcs using ~/.cache/darcs/ instead of ~/.darcs/cache. Unless $XDG_CACHE_HOME is set, in which case it will use $XDG_CACHE_HOME/darcs/. If $XDG_CACHE_HOME is set but does not exist, or if it is not set and ~/.cache does not exist, the missing directory is created with permissions 0700. Under for Mac OSX, this patch makes darcs use the directory ~/Library/Caches/, which is the current norm. Can someone using Mac OSX please try it? Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] conflict but no markers
HI, Three of these files actually contain conflict markers, but the third one (./src/seq/seq_if.c) does not. Even so, most of the changes that I expected to see in the file are not there, so it seems Darcs acted as if I had said --no-mark-conflicts. Could it be that the conflict with ./src/seq/seq_if.c be not a hunk conflict but a move, delete, whatever conflict? This may explain why there are no markers. Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] Mac OSX testers wanted: darcs unstable uses standard cache location
Thanks for testing! I wonder if we should do something similar with ~/Library/Preferences You mean moving the contents of ~/.darcs to ~/Library/Preferences/darcs, and also ~/.darcs to ~/.config/darcs under Linux ? Darcs should do the move automatically then. Contrary to the cache, the preference files of darcs do not move by themselves. g. ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] contributing to the darcs manual
Hi Iva, sorry for the late response! The manual of darcs is going to change a lot for the next release (2.10). The one that is available on-line corresponds to darcs 2.8, it is generated from latex files that used to be in darcs' repository. As it got more and more out of date (with respect to darcs itself and the wiki) we decided to remove it. Instead we added `darcs help markdown`, a command to generate a reference manual of all commands, environment variables and patterns of darcs, in the markdown format. The code to generate it is in src/Darcs/UI/Commands/Help.hs. We did this in the February sprint. With this reference manual and some parts that we could directly edit on the wiki (which is also in markdown), we could easily generate a manual in various formats (html, pdf, ebook). The structure is not clearly defined and this will most probably deserve a discussion on darcs-users before 2.10. So about the Emacs and Resolution piece of documentation, I think they belongs to the wiki. Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] darcs news #104
# News and discussions 1. Google Summer of Code 2013 has begun! BSRK and José will post updates on their blogs: - http://bsrkaditya.blogspot.com/search/label/darcs - http://blog.jlneder.com.ar/search/label/darcs # Issues resolved (8) issue2163 Radoslav Dorcik ~ - new option for amend, select author for patch stealing. - http://bugs.darcs.net/issue2163 issue2227 Ganesh Sittampalam ~ - move the rebase patch to the end before an amend-record - http://bugs.darcs.net/issue2227 issue2248 Ganesh Sittampalam ~ - always clean up rebase-in-progress state - http://bugs.darcs.net/issue2248 issue2250 BSRK Aditya ~ - tabbing in usageHelper - pad by max length of command name - http://bugs.darcs.net/issue2250 issue2311 Sebastian Fischer ~ - posthook for 'get' should run in created repo - http://bugs.darcs.net/issue2311 issue2312 Sebastian Fischer ~ - posthooks for 'record' and 'amend-record' should receive DARCS_PATCHES - http://bugs.darcs.net/issue2312 issue2320 Jose Luis Neder ~ - save prompted author name in ~/.darcs/author instead of ./_darcs/prefs/author - http://bugs.darcs.net/issue2320 issue2321 Jose Luis Neder ~ - when no patch name given, directly invoke text editor - http://bugs.darcs.net/issue2321 # Patches applied (20) 2013-06-09 Guillaume Hoffmann ~ - make nano the default text editor instead of vi 2013-06-20 BSRK Aditya ~ - Resolve issue2250: tabbing in usageHelper - pad by max length of command name 2013-06-16 Guillaume Hoffmann ~ - remove word repetition in fileHelpAuthor string 2013-06-16 Jose Luis Neder ~ - resolve issue2320: save prompted author name in ~/.darcs/author instead of ./_darcs/prefs/author - resolve issue2321: when no patch name given, directly invoke text editor 2013-04-30 Guillaume Hoffmann ~ - remove repository flag DryRun parameter when not used or always NoDryRun 2013-04-05 Ganesh Sittampalam ~ - fix test for Windows 2013-03-10 Sebastian Fischer ~ - Follow-up on patch1066 resolving issue2312. - resolve issue2312: posthooks for 'record' and 'amend-record' should receive DARCS_PATCHES - Added tests for issue2312: posthooks for 'record' and 'amend-record' should receive DARCS_PATCHES 2013-02-16 Ganesh Sittampalam ~ - resolve issue2227: move the rebase patch to the end before an amend-record - tidy command definitions in Darcs.UI.Commands.Rebase - resolve issue2248: always clean up rebase-in-progress state - add --ignore-times option to rebase commands that read the working dir 2013-03-08 Sebastian Fischer ~ - resolve issue2311: posthook for 'get' should run in created repo - Added tests for Issue 2311. 2013-06-03 Guillaume Hoffmann ~ - haddocks for functions that look for user e-mail 2013-03-02 Radoslav Dorcik ~ - Resolve issue2163: new option for amend, select author for patch stealing. 2013-05-29 BSRK Aditya ~ - Export doOptimizeHTTP from Optimize module - Increase efficiency of patch index update by more efficient extraction ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] [darcs-devel] [issue2321] remove Do you want to add a long comment? prompt
To clarify the current proposal, I renamed the issue on the bug tracker to when no patch name given, directly invoke text editor. ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] getSymbolicLinkStatus: does not exist
What I recollect from your message, however, is that you point out a general issue of Robustness with darcs, and I agree with this. Especially robustness as perceived by casual users. I personally find Darcs quite reliable in my day-to-day experience. Yes, that's exactly the issue. As regular users we forget about the first impression we had. We get used to work around flaws. Hence the report you mentioned in your first mail is particularly useful! Another idea, but maybe this is silly: what about adding a Don't like button, which people can click on if they think this issue is particularly annoying (or looks like it gives Darcs a bad reputation)? Though that is probably a bit difficult to add to roundup. What you describe makes me think of the star button on issues of Google Code (see for instance https://code.google.com/p/clementine-player/issues/list). This would require people to have an account on bugs.darcs.net for this to work (if we want to avoid spam), and we don't really have a lot of active users on bugs.darcs.net anyway :-/ Not sure it's worth it... Something we need would be someone to occupy the job of Issue Manager: http://darcs.net/DarcsTeam#issue-manager . Eric is supposed to do it but he does not have a lot of time on his hands. If you want to fill in and dedicate yourself to triage/prioritize issues, you're very welcome! :-) Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] Fwd: [Haskell-cafe] [haskell.org Google Summer of Code 2013] Approved Projects
Congratulations to BSRK Aditya and José Neder, our Google Summer of Code students of 2013! They will work until end of September on the following projects: * http://darcs.net/GSoC/2013-Darcsden ( BSRK Aditya, mentored by Ganesh ) * http://darcs.net/GSoC/2013-BetterRecord ( José Neder, mentored by me ) Soon they will start to blog about their projects, so stay tuned on planet.darcs.net for updates! Many thanks to Edward Kmett and Haskell.org for enabling darcs to have two slots this year. (And Google of course). Guillaume -- Forwarded message -- From: Edward Kmett ekm...@gmail.com Date: 2013/5/28 Subject: [Haskell-cafe] [haskell.org Google Summer of Code 2013] Approved Projects To: Haskell Cafe haskell-c...@haskell.org We've worked our way through the project approval process for another year. This year we accepted 9 projects for haskell.org in general and are hosting 2 additional projects for darcs as an umbrella organization. haskell.org: * Parallelise 'cabal build' by Mikhail Glushenkov, mentored by Johan Tibell * Extending GHC to support building modules in parallel by Patrick Palka, mentored by Thomas Schilling * Communicating with mobile devices by Marcos Pividori, mentored by Michael Snoyman * Improve Haddock Markup and Capabilities by Fūzetsu, mentored by Simon Hengel * Haskell Qt Binding Generator by Zhengliang Feng, mentored by Carter Schonwald with help from Ian-Woo Kim * Improve the feedback of the cabal-install dependency solver by Martin Ruderer, mentored by Andres Löh * Interactive-diagrams and a paste site with the ability for dynamic rendering of diagrams by Dan Frumin, mentored by Luite Stegeman * Overloaded record fields for GHC by Adam Gundry, mentored by Simon Peyton-Jones * Port Charts to use Diagrams by Jan Bracker, mentored by Tim Docker darcs: * Better record command for darcs by José Neder, mentored by Gillaume Hoffmann * Enhancing Darcsden by BSRK Aditya, mentored by Ganesh Sittampalam Students have from now through Jun 16th to get up to speed and get to know their mentors. And while the summer of code officially starts on Jun 17th, keep in mind that the mid-term evaluations aren't that much farther behind, starting July 29th, so you'll want to hit the ground running. If you put in a project proposal and it wasn't accepted and/or you would like feedback, please feel free to email me or contact me on the #haskell-gsoc channel on irc.freenode.net. We received more proposals than slots this year, and so we were forced to make a few hard decisions. Shachaf Ben-Kiki is helping out as this year's backup administrator and he should also be able to help out with administrivia or questions as well. I'd like to thank everyone for participating in the selection process and I think we can look forward to another excellent summer of code! Edward Kmett haskell.org Google Summer of Code Administrator ___ Haskell-Cafe mailing list haskell-c...@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] getSymbolicLinkStatus: does not exist
Hi Ben, First, since you are aware that we all have little time to dedicate to darcs, you should try to send shorter, more synthetic mails. What I recollect from your message, however, is that you point out a general issue of Robustness with darcs, and I agree with this. The problems you mention have already been noticed: there's a ticket open in the bug tracker about the strange filename bug (http://bugs.darcs.net/issue2061), and I wrote a summer of code project proposal on http://darcs.net/GSoC about improving the cache system (which you are free to expand since it has not been chosen this year). What happens is that none of these issues seem to be anyone's lowest hanging fruit. We all lack time, but what we can do is go step by step towards making these issues easier to solve. For instance for http://bugs.darcs.net/issue2061, one could start tackling the issue by looking at where does the error come from (in the source code), and reporting it on the bug tracker. Then someone (else) may start thinking that this is an easy issue, and is going to actually write a fix. An also, maybe we could add a Robustness category to the bug tracker, for those issues that make darcs seem flaky? Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] [darcs-devel] [issue2321] remove Do you want to add a long comment? prompt
Alright, I believe we want to make this change: make that darcs record without -m flag directly launches the long description editor. This would make darcs behave similarly to most other VCS. Definitely a probably-easy change to do. ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] GSoC Proposal - Better record command
Hi everyone, Marcio told me that he finally will not be able to apply to GSoC this year :-( The good news is that we have an application that has already received a good amount of feedback (from Owen but also from me offline), and that can be reused by anyone who is interested. So please go ahead if you find the project better record interesting! Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] darcs weekly news #103
# News and discussions 1. Darcs will be participating to this year's Google Summer of Code under the umbrella of Haskell.org! If you are interested please consult the ideas page and contact us: - http://darcs.net/GSoC 2. Sebastian Fischer implemented `darcs-history`, a program to be used as darcs posthook and that tracks patch movements inside of a repository: - http://lists.osuosl.org/pipermail/darcs-devel/2013-February/014754.html - http://lists.osuosl.org/pipermail/darcs-devel/2013-February/014898.html - http://www.informatik.uni-kiel.de/~sebf/darcs/darcs-history/README.html 3. Sebastian also suggested the possibility for darcs to easily split and merge patches that are depended upon: - http://lists.osuosl.org/pipermail/darcs-devel/2013-March/014965.html 4. Piyush P Kurur was also interested in some special kinds of deep `amend-record`: - http://lists.osuosl.org/pipermail/darcs-users/2013-March/026838.html # Issues resolved in the last week (1) issue2274 Guillaume Hoffmann ~ - create patch index only with commands that take a lock - http://bugs.darcs.net/issue2274 # Patches applied in the last week (27) 2013-02-15 Ganesh Sittampalam ~ - rename iconv functions imported from haskeline to avoid name clash - accept issue2293: patch index update reads too much of the repo - switch from sleep to threadDelay to fix warning 2013-02-22 Guillaume Hoffmann ~ - set timeout to 1 second in expire-unused-caches test 2013-02-25 Ganesh Sittampalam ~ - make --no-interactive an alias for --all 2013-02-21 Florent Becker ~ - Make darcs changes interactive by default (darcs log is non-interactive) - Mark issue1105 as failing again 2013-01-02 Ganesh Sittampalam ~ - test for issue2286: make sure we can read repos with non-UTF8 metadata 2013-02-22 Guillaume Hoffmann ~ - warn earlier when DARCS_CONNECTION_TIMEOUT is not a number - correctly set curl connection timeout - no longer enable changes and annotate to create patch index - Resolve issue2274: create patch index only with commands that take a lock - improve output of get with and without --verbose - enable get --packs by default again - remove trackdown-bisect.sh long tests - less confusing apply --skip-conflicts message when everything conflicts 2013-01-01 Ganesh Sittampalam ~ - We can use chcp to switch encodings on Windows - unsetting DARCS_TEST_PREFS_DIR in utf8 test doesn't seem to be necessary - improve diagnostics when utf8 test fails - windows test fix: replace shell script with a Haskell program - disable join tests on Prim.V3 patches as it doesn't support join yet - remove a couple of quickCheck tests that can never work - bump cryptohash dependency 2013-04-10 Owen Stephens ~ - accept issue1577 - revert deletes new files 2013-02-16 Ganesh Sittampalam ~ - simplify test case 2013-03-01 Owen Stephens ~ - accept issue2310: rollback rmfile doesnt re-add in pending - Accept issue2308 ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] darcs weekly news #102
# News and discussions 1. Darcs 2.8.4 was released. It supports GHC 7.6 and fixes `get --tag`: - http://lists.osuosl.org/pipermail/darcs-users/2013-February/026769.html 2. Here is the report from the 8th darcs hacking sprint: - http://blog.darcs.net/2013/02/darcs-hacking-sprint-8-report.html # Issues resolved in the last week (6) issue904 Nathaniel Filardo ~ - Fix record on Linux/FUSE/sshfs (fall back to sloppy locks automatically) - http://bugs.darcs.net/issue904 issue2155 Dave Love ~ - Expurgate the non-functional annotate --xml-output option - http://bugs.darcs.net/issue2155 issue2270 Sebastian Fischer ~ - fixed darcs changes -i --only-to-files - http://bugs.darcs.net/issue2270 issue2277 Radoslav Dorcik ~ - rebase suspend and unsuspend supports --summary. - http://bugs.darcs.net/issue2277 issue2282 Ganesh Sittampalam ~ - don't allow remote operations to copy the rebase patch - http://bugs.darcs.net/issue2282 issue2287 Radoslav Dorcik ~ - obliterate -O doesn't overwrite existing file. - http://bugs.darcs.net/issue2287 # Patches applied in the last week (77) 2013-02-21 Guillaume Hoffmann ~ - use many-files premade repos in get-http-packed tests to go faster - reintroduce DARCS_CONNECTION_TIMEOUT doc, talk about undocumented env vars 2013-02-18 Ganesh Sittampalam ~ - rename FileMod - [Patch]Index 2013-02-20 Guillaume Hoffmann ~ - haddock for commandCommand AbsolutePath arguments 2013-02-18 Ganesh Sittampalam ~ - work around missing feature in haddock 2013-02-17 Guillaume Hoffmann ~ - make README.test_maintainers.txt point to the appropriate wiki page - tests: check if darcs-1 in .darcs/defaults instead of hashed, and no longer check OF - rm testing old-fashioned repo with checkpoint, since what we test already fails because it's OF - display error message when using init --hashed - darcs-test UI: print Darcs1 in place of Hashed - fix tests after changing --hashed into --darcs-1 - rename init --hashed into init --darcs-1 2013-02-17 Ganesh Sittampalam ~ - a bit of code tidying in Darcs.UI.Commands.Rebase 2013-02-16 Radoslav Dorcik ~ - Resolve issue2277: rebase suspend and unsuspend supports --summary. 2013-02-16 Ganesh Sittampalam ~ - tidy imports in Darcs.UI.Commands.Rebase - make rebase reify/inject hidden - get rid of withGutsOf which is now redundant 2013-02-16 Guillaume Hoffmann ~ - document DARCS_GET_FOO and DARCS_APPLY_FOO - include patterns help to help markdown output - fix markdown and titles in help markdown - DARCS_SLOPPY_LOCKS help 2013-02-16 Radoslav Dorcik ~ - include environment variables in `darcs help markdown` output. - Ressurection of environment vars desciption from the manual. 2013-02-15 Ganesh Sittampalam ~ - add a few more tests of darcs changes with moved files - cosmetic cleanups: remove unnecessary -A in test script and trailing whitespace - Windows fix for issue2270 test 2013-02-10 Sebastian Fischer ~ - resolve issue2270: fixed darcs changes -i --only-to-files - added tests for issue 2270 2013-02-16 Ganesh Sittampalam ~ - issue1932 test: we can still test the remote parts on Windows - TAG 2.9.7 - issue1932 test can't possibly work on Windows - need different path separator on Windows - add missing -DWIN32 for test harness - bump version to 2.9.7 2012-12-21 Owen Stephens ~ - Improve error message for bad match patterns - Rename a test 2013-02-16 Radoslav Dorcik ~ - facility for getting unique path name based on base name (base_n) 2013-02-16 Guillaume Hoffmann ~ - reintroduce missing when 2013-02-16 Radoslav Dorcik ~ - test for issue2287 is successful. - Resolve issue2287: obliterate -O doesn't overwrite existing file. 2013-01-15 Guillaume Hoffmann ~ - Remove FixFilePath from DarcsFlag 2013-02-16 Radoslav Dorcik ~ - Get command uses new unique name facility. - Add failing test for issue2287 2013-02-16 Ganesh Sittampalam ~ - resolve issue2282: don't allow remote operations to copy the rebase patch 2013-02-16 Owen Stephens ~ - Accept issue2256 - diff with empty arg string causes failure in updateIndex 2013-02-15 Guillaume Hoffmann ~ - fix network tests that did not find the right darcs executable - update lazy-get.sh test to an existing small remote repo 2008-07-11 Nathaniel Filardo ~ - Resolve issue904: Fix record on Linux/FUSE/sshfs (fall back to sloppy locks automatically) 2013-01-18 Ganesh Sittampalam ~ - import encoding code from haskeline: cabal changes - import encoding code from haskeline: switch over - ROLLBACK: use bytestring-handle instead of haskeline for encoding - use bytestring-handle instead of haskeline for encoding - import encoding code from haskeline: Setup.lhs changes - add
[darcs-users] make `darcs changes` interactive by default?
What about we finally make `darcs changes` interactive by default? And (as suggested by Florent on IRC) map 'y' to 'p' (use `less`) instead of 'v' as of now. ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] Darcs Hacking Sprint #8 (February 15-17, Paris)
Interesting! I'm leaving for the sprint now, but do you think you can write a nice README.md file that would describe the installation steps, and the current / planned features of your project ? thanks. ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] darcs weekly news #101
# News and discussions 1. Confirmed: the next Hacking Sprint will be in IRILL, Paris on February 15, 16 and 17: - http://darcs.net/Sprints/2013-02 - http://www.irill.org/ 2. Darcs HEAD has been fixed to work with GHC 7.6 without encoding bugs, go ahead and try it! - http://bugs.darcs.net/issue2286 - http://hub.darcs.net/darcs/darcs-screened/patch/20130118225947-81bb2 # Issues resolved in the last week (4) issue2199 Ganesh Sittampalam ~ - getMatchingTag needs to commute for dirty tags - http://bugs.darcs.net/issue2199 issue2236 Gian Piero Carrubba ~ - make 'n' an alias for 'q' in lastregret questions - http://bugs.darcs.net/issue2236 issue2238 Gian Piero Carrubba ~ - let optsModifier remove all occurrences of LookForAdds - http://bugs.darcs.net/issue2238 issue2247 Ganesh Sittampalam ~ - move patch index creation into the job running code - http://bugs.darcs.net/issue2247 # Patches applied in the last week (45) 2012-12-30 Ganesh Sittampalam ~ - add some comments about nearby darcs, and print out the one that was found - make darcs-test look nearby for a darcs exe to use - canonize myself in .authorspellings - minor refactoring - Expose some of the innards of ShowAuthors for use in the API - Don't expose intermediate details externally in Darcs.Patch.Annotate - annotate needs to use posix filepaths - provide a better error message on failure - be a bit more robust when deleting the patch index 2012-12-20 BSRK Aditya ~ - Report an error if --disable-patch-index fails 2012-12-28 Ganesh Sittampalam ~ - fix test on windows: replace shell script with haskell program - need to do case-insensitive comparison on Windows 2012-10-19 Mark Stosberg ~ - PatchIndex: Add test coverage for a patch-indexed repo being accessed by older darcs. - Start documenting key flags in README. 2012-11-11 Ganesh Sittampalam ~ - bump version to 2.9.6 - TAG 2.9.6 - need to treat paths in prefs/binaries as Posix, even on Windows 2012-09-29 Owen Stephens ~ - Implement Repository/Prefs.normalise in terms of standard FilePath functions 2012-10-26 Ganesh Sittampalam ~ - get rid of unsafePerformIO in cleanLocalDate - get rid of unused readLocalDate 2012-12-21 Owen Stephens ~ - Refactor implementation of environment help 2012-12-19 Gian Piero Carrubba ~ - avoid displaying 'Unknown ...' in the output of `darcs help environment` 2012-11-11 Ganesh Sittampalam ~ - break out Darcs.Util.AtExit from Darcs.Util.Global - move remains of Darcs.Util to be Darcs.Util.File 2012-09-15 Eric Kow ~ - Remove redundant Module field from module haddocks. 2012-11-02 Ganesh Sittampalam ~ - break out Darcs.Util.Environment - move breakCommand into Darcs.Util.Text - break out Darcs.Util.Exception from Darcs.Util - break out Darcs.Util.Prompt from Darcs.Util - break out Tree functions from Darcs.UI.Commands.Util - break Darcs.Util.Ssh out from Darcs.Util.Global - resolve issue2247: move patch index creation into the job running code - test that patch index is re-created if not present - resolve issue2199: getMatchingTag needs to commute for dirty tags 2012-12-13 Gian Piero Carrubba ~ - resolve issue2236: make 'n' an alias for 'q' in lastregret questions 2012-12-18 Ganesh Sittampalam ~ - tweak test to make sure that patches are actually selected - fix test following change in output - fix test for Windows - use throwIO instead of throw - restrict imports - provide verbose diagnostics for can't suspend - replace debug function in ssh Connection with string - reorganise use of unsafePerformIO in transcoding a bit - replace instance Show Doc with an explicit function 2012-12-16 Gian Piero Carrubba ~ - resolve issue2238: let optsModifier remove all occurrences of LookForAdds ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] next darcs sprint, February-March 2013?
After more chatting and asking, it has been confirmed that the sprint will take place on February 15-17, in IRILL, Paris! see you there ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] next darcs sprint, February-March 2013?
After some chatting on IRC we concluded that the next sprint will be: * on February 22-24 * in Paris or Southampton or (if I can get in contact with people from there) Lille. Let's give us one more week to see the options of place. In the meantime, if more people want to participate, just shout. Guillaume ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] next darcs sprint, February-March 2013?
Hi, I'll be in Europe next February and (beginning of) March. Maybe we could arrange a sprint during this period? The event can be hosted in Nancy, France [1] (where I'll be staying) or we can do it again at the IRILL in Paris, like in spring of 2011 [2]. My possible dates would be in February 8-10, 15-17, 22-24, and March 1-3 (each time friday to sunday). If you intend to go or if you have suggestions of places and dates, let us discuss this before February. Guillaume [1] https://en.wikipedia.org/wiki/Nancy,_France [2] http://darcs.net/Sprints/2011-04 ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] darcs weekly news #98
# News and discussions 1. News from Aditya's Summer of Code work on patch index: - http://bsrkaditya.blogspot.com.ar/2012/06/gsoc-patch-index-week-2.html - http://bsrkaditya.blogspot.com.ar/2012/06/gsoc-patch-index-week-3-4.html - http://bsrkaditya.blogspot.com.ar/2012/06/gsoc-patch-index-week-5.html - http://bsrkaditya.blogspot.com.ar/2012/07/gsoc-patch-index-week-6.html - http://bsrkaditya.blogspot.com.ar/2012/07/gsoc-patch-index-week-7.html 2. We are now using the wiki as the home page. Be sure to visit it and give us feedback: - http://darcs.net 3. Eric Kow documented the workflow of having a group of users working with the same repository: - http://lists.osuosl.org/pipermail/darcs-users/2012-June/026523.html - http://darcs.net/Using/GroupRepo # Issues resolved in the last week (3) issue2193 Guillaume Hoffmann ~ - make that finalizeTentativeChanges no longer run tests - http://bugs.darcs.net/issue2193 issue2198 Guillaume Hoffmann ~ - move repo testing code to Darcs.Repository.Test - http://bugs.darcs.net/issue2198 issue2200 Owen Stephens ~ - darcs replace complains if no filepaths given - http://bugs.darcs.net/issue2200 # Patches applied in the last week (70) 2012-07-04 Guillaume Hoffmann ~ - update help strings of --hashed and --darcs-2 - move functions from Darcs.Utils to Repository and UI modules 2012-07-10 Owen Stephens ~ - Fix an implementation style wart in Replace, from fix for issue2125. 2012-07-09 Guillaume Hoffmann ~ - update darcs wiki repository url 2012-06-27 Owen Stephens ~ - Remove reference to old patch-name flag in amend help 2012-07-02 Guillaume Hoffmann ~ - delete remaining tests for rollback --record, fix pull.sh - remove rollback --record functionality - use nubSort function from data-ordlist instead of own 2012-07-01 Eric Kow ~ - Simplify issue2200 test (Fails on Mac otherwise) 2012-06-21 Guillaume Hoffmann ~ - move Darcs.Witnesses to Darcs.Patch.Witnesses - remove redundant hashed_inventory creation during get - move Darcs.Flags to Darcs.UI.Flags - remove Darcs.Flags import from all Darcs.Repository* modules - remove Darcs.Flags import from Darcs.Repository.State - remove Darcs.Flags import from Darcs.Repository.Motd - remove Darcs.Flags import from Darcs.Repository.Prefs - remove Darcs.Flags import from Darcs.Repository.Format - remove Darcs.Flags import from Darcs.Repository.Test - remove DarcsFlag from Repository datatype, use Darcs.Repository.Flags more - introduce Darcs.Repository.Flags and start using it - remove Darcs.Patch.Match dependency on Darcs.Flag - explicit imports for Darcs.Patch.Match - fix compilation on non-windows oses after Patchy change 2012-05-17 Ganesh Sittampalam ~ - Darcs.Patch.Invert: missing newline at end of file - make Patchy smaller - use RepoPatch instead of Patchy constraint for matchers - relax type signature - add merge combinators - add utility function for changing type of a ListFormat - add commutation combinators for Named - drop unnecessary superclasses and move Invert FL/RL instances - break CommuteFn infrastructure out into separate module - add helper class for debugging patches - drop MyEq superclass from Patchy - get rid of joinPatches - drop some unnecessary Patchy constraints 2012-05-31 Guillaume Hoffmann ~ - finer-grained import for Darcs.Repository.Match - move Darcs.ProgressPatches to Darcs.Patch.Progress - move MonadProgress into Darcs.Patch 2012-05-31 Ganesh Sittampalam ~ - move formatText out from GZCRCs into Utils 2012-05-31 Guillaume Hoffmann ~ - move Compat and Diff to Repository, start taking apart Darcs.Utils 2012-06-08 Alejandro Gadea ~ - Hlint suggestion. 2012-05-30 Ganesh Sittampalam ~ - fix build on Windows - accept issue2199: darcs get --tag gets too much - fix warning that was showing up on Windows 2012-05-26 Eric Kow ~ - Eric no longer at University of Brighton. 2012-05-16 Ganesh Sittampalam ~ - add comment about a dubious looking bit of code 2012-05-29 Guillaume Hoffmann ~ - move Email External PrintPatch and SelectChange into UI - move function getTermNColors from D.External to D.ColorPrinter - move RemoteApply to UI - split Match in Repository-specific and Patch-specific modules - move Resolution into Repository - introduce and populate the UI module, move Annotate into Patch - rm Darcs.Patch.MatchData making patterns simply String, style Arguments - move function showFriendly from Darcs.Arguments to Darcs.PrintPatch - make that no repository-related modules depend on Darcs.Arguments - move malicious path test functions from Darcs.CommandAux to Darcs.Path - split External
Re: [darcs-users] website/wiki front page
Hi Eric, if you know how to make darcs.net redirect to the wiki and keep on serving the screened and reviewed repositories at the same place, why not. Otherwise we will have to wait until we have a working den.darcs.net and more all of our repos over there (which I think would be something we should try). g. ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] website/wiki front page
I've converted the 'thanks' and 'donations' pages as wiki pages. I don't think we need to make redirections from their old URL to these wiki pages. In the 'donation' page I couldn't copy the javascript piece of code for google checkout, but donating with this widget seems to work anyway. I can't help about the apache config that would enable both redirecting to the wiki and serving the darcs repositories. Maybe we will move all repos to {hub,den}.darcs.net when it's usable? g. ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] website/wiki front page
For those who haven't followed, we are trying to move some things out of darcs' darcs repository. One of these things is the website homepage, that we're trying to embed into the wiki. We dicussed the topic on darcs-devel (the topic was tackled among many other things, see Eric's answer to the thread how to make darcs dev more agile [1] for an answer to the website/wiki issue). So, following that conversation I've: * made the wiki front page editable only via darcs push (disabling web edition) since we received spam from time to time on it (that's a simple change in the gitit configuration) * imported the home page into the wiki front page, removing some parts that were redundant with the wiki links that were already there * imported the css into the wiki css, tweaking it a little beat (I like the fixed width now) What would be nice to change * prevent the wiki from displaying a title for the front page. I don't know whether it's possible to make gitit to that. * move the login/get account link to the left, below what's already there * move the tabs to the left. is it possible? * reintroduce some quick start examples to the right, below the news Have a look at http://wiki.darcs.net/ . A potential issue is that a website front page and a wiki front page may not have the same content. This is why I've moved the quick start to http://wiki.darcs.net/QuickStart , but a succint version of it may appear in the wiki front page, I think (as in the home page of Mercurial [2]?) . Also the camp youtube video did not work once copied on the wiki, so I simply removed it. Other links present on darcs.net were already in the wiki front page, so I've simply removed them. Simon, don't hesitate to revert, move and tweak stuff as you prefer. Do you have ssh access to the wiki? Ask Eric if you don't. Once it looks good, and without waiting too much, I think it makes sense to make the whole wiki appear under www.darcs.net, and to remove website generation from darcs' darcs repository (manual generation should stay for the moment). guillaume [1] http://lists.osuosl.org/pipermail/darcs-devel/2012-May/013901.html [2] http://mercurial.selenic.com/ ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] darcs weekly news #97
# News and discussions 1. News from Summer of Code -- BSRK Aditya posted his first entry about his work on patch index: - http://bsrkaditya.blogspot.com.ar/2012/05/gsoc-patch-index-week-1.html 2. Meanwhile, an optimization of 'darcs diff' written by Petr Rockai has been ported to HEAD: - http://lists.osuosl.org/pipermail/darcs-users/2012-May/026519.html # Issues resolved in the last week (0) # Patches applied in the last week (24) 2012-05-16 Owen Stephens ~ - Accept issue1959 unwritable cache should not kill darcs 2012-05-26 Eric Kow ~ - Improve issue2193 test style. - Improve issue2187 test style. 2012-05-01 Ilya Permonov ~ - Accept issue2193: darcs apply --test runs the test twice. - Accept issue2187: darcs apply --test patch-set crashes if the test fails. - Accept issue2186: apply --reply is broken. 2012-05-18 Guillaume Hoffmann ~ - remove inventory code of optimize without --reorder flag since it did nothing 2012-05-15 Ganesh Sittampalam ~ - resolve conflicts in cabal version field - bump version to 2.8.1 and update NEWS - resolve conflict in mtl dependency bump - bump mtl dependency 2012-04-22 Florent Becker ~ - bump version to 2.8.0 2012-04-07 Ganesh Sittampalam ~ - Bump version to 2.7.99.2 2012-03-30 Florent Becker ~ - Change version to 2.7.99.1 2012-05-14 Ganesh Sittampalam ~ - darcs-users - darcs-devel - update NEWS with 2.8 release notes 2012-05-24 Guillaume Hoffmann ~ - haddock for fixUrl and fix 2 haddocks - make darcs apply work with url - kill footnotes in manual and uninformative command-overview paragraph 2012-05-18 Michael Hendricks ~ - Fix show-authors test on OS X 2012-05-16 Owen Stephens ~ - Tidy/Style ShowAuthors - Add missing -f flag to rm in show-authors test - Add rank to show authors - Accept issue2179 darcs diff no longer works given a dir path ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] optimization in HEAD: darcs diff
I'd like to share to the darcs-users list another significant change in HEAD that happened after the release of Darcs 2.8, this time an optimization. In 2010 Petr Rockai optimized the darcs diff command, but a few things blocked the inclusion of this piece of code into darcs. Notably, the optimization did not support old-fashioned repositories. However, since version 2.8 Darcs no longer fully support these repositories, so the new implementation of diff has been ported to HEAD. As in Petr's words (http://bugs.darcs.net/patch351): 8 I have changed the diff code to only write those files that actually changed in the temporary locations. On my other project (less than 1000 working copy files): (with cold cache) head: darcs diff 1,09s user 0,58s system 9% cpu 16,752 total now: darcs diff 0,14s user 0,04s system 6% cpu 2,978 total (with hot cache) head: darcs diff 0,36s user 0,18s system 98% cpu 0,548 total now: darcs diff 0,06s user 0,01s system 86% cpu 0,078 total 8 I've added more informal benchmarks at the end of this mail. So, if you want to build a darcs from HEAD and discover again darcs diff, have a go at it and see how fast it has become! If you are using an external diffing tool, you can use the new flag --no-pause-for-gui (http://bugs.darcs.net/patch748) implemented by Michael Hendricks. Following the switch to this new implementation, Owen Stephens noticed that diffing directories no longer worked (http://bugs.darcs.net/issue2179) but Yuriy Vostrikov soon sent a patch fixing this issue (http://bugs.darcs.net/patch818). If you find more bugs, please let us know! Guillaume -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Informal benchmarks on http://darcs.net/ between darcs 2.8 and current HEAD. (time darcs diff is run until the time ouput becomes consistent, ie, benchmarks are done on hot disk cache). Last patch in HEAD (kill footnotes): 2.8 real0m0.598s user0m0.380s sys 0m0.190s HEAD real0m0.194s user0m0.180s sys 0m0.010s With a patch deeper in the history (update NEWS log with 2.5.1) 2.8 real0m4.424s user0m1.550s sys 0m1.300s HEAD real0m1.342s user0m1.250s sys 0m0.090s Even older (patch Import bracketOnError from Workaound from 2006): 2.8 real1m17.442s user0m17.650s sys 0m16.960s HEAD real0m18.054s user0m17.670s sys 0m0.370s ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] optimization in HEAD: darcs diff
A few memory allocation figures obtained with +RTS -s for two cases (recent patch and old patch): * patch kill footnotes (latest): 2.8 287,535,128 bytes allocated in the heap 59,356,640 bytes copied during GC 14,969,680 bytes maximum residency (9 sample(s)) 342,752 bytes maximum slop 32 MB total memory in use (0 MB lost due to fragmentation) [..] %GC time 17.5% (16.5% elapsed) Alloc rate871,318,569 bytes per MUT second Productivity 82.5% of total user, 59.8% of total elapsed HEAD 62,756,136 bytes allocated in the heap 37,237,544 bytes copied during GC 12,593,440 bytes maximum residency (6 sample(s)) 332,928 bytes maximum slop 24 MB total memory in use (0 MB lost due to fragmentation) [..] %GC time 0.0% (38.1% elapsed) Alloc rate697,290,400 bytes per MUT second Productivity 100.0% of total user, 64.1% of total elapsed * patch Import bracketOnError from Workaound from 2006: 2.8 17,413,824,480 bytes allocated in the heap 1,306,485,280 bytes copied during GC 10,460,976 bytes maximum residency (173 sample(s)) 1,761,112 bytes maximum slop 30 MB total memory in use (0 MB lost due to fragmentation) [..] %GC time 7.4% (3.3% elapsed) Alloc rate1,225,462,665 bytes per MUT second Productivity 92.6% of total user, 18.8% of total elapsed HEAD 14,516,729,880 bytes allocated in the heap 1,906,137,160 bytes copied during GC 174,140,552 bytes maximum residency (20 sample(s)) 26,304,952 bytes maximum slop 430 MB total memory in use (0 MB lost due to fragmentation) [..] %GC time 26.7% (34.7% elapsed) Alloc rate1,131,467,644 bytes per MUT second Productivity 73.3% of total user, 71.6% of total elapsed ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
Re: [darcs-users] new feature in HEAD: exponential backoff test strategy
I've updated the wiki page which url is now http://wiki.darcs.net/Using/Test . g. ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
[darcs-users] darcs weekly news #96
# News and discussions 1. Darcs 2.8.1 was released, the only change is a build dependency that will make it buildable with the next Haskell Platform: - http://lists.osuosl.org/pipermail/darcs-users/2012-May/026506.html - http://hackage.haskell.org/package/darcs-2.8.1 2. Meanwhile in HEAD, a new test strategy has been implemented: - http://lists.osuosl.org/pipermail/darcs-users/2012-May/026503.html 3. On the developers' mailing list, we are discussing how to make the darcs development process more friendly: -http://lists.osuosl.org/pipermail/darcs-devel/2012-May/013820.html # Issues resolved in the last week (3) issue1921 Owen Stephens ~ - return Nothing in splitOnTag if the tag isn't in the patchset - http://bugs.darcs.net/issue1921 issue2095 Ganesh Sittampalam ~ - avoid new GHC encoding behaviour using a global setting - http://bugs.darcs.net/issue2095 issue2161 Owen Stephens ~ - - don't use a separate type-variable for recorded/tentative in WhatsNew - http://bugs.darcs.net/issue2161 # Patches applied in the last week (77) 2012-05-14 Simon Michael ~ - home page: 2.8.1 release, trim news 2012-04-01 Ganesh Sittampalam ~ - enable issue1763 test on Windows as it seems to work - resolve conflicts in GHC encodings fix - resolve issue2095: avoid new GHC encoding behaviour using a global setting - resolve conflict between issue2161 fix and witness macro removal 2012-03-21 Owen Stephens ~ - resolve issue2161 - don't use a separate type-variable for recorded/tentative in WhatsNew 2012-05-12 Simon Michael ~ - home page: link hosting sites as suggested by Radoslav Dorcik 2012-04-21 Marc Simpson ~ - Add new 'usageInfo' implementation (Darcs.Usage); employ in Darcs.Command. 2012-05-12 Guillaume Hoffmann ~ - Accept issue2138 whatsnew --summary not reporting conflicts - fix duplicate appearance of darcs test in manual - fix failing test for issue2100 - make exit code of darcs add non-zero if any adds fail 2012-01-19 Ganesh Sittampalam ~ - resolve conflict in version number - TAG 2.9.1 - bump version to 2.9.1 2011-09-07 Eric Kow ~ - Accept issue2100: darcs add should move on from first failure. 2012-05-10 Simon Michael ~ - home page: trim news - home page: update news - site: more css color cleanup - home page: or tweak - site: border color fix - site: css cleanups, pre bottom border - home page: move or - site: underline links only on hover - update Summersault thanks per markstos - home page: box shadow for examples, add the dark bg style but don't use it - home page: less top padding, splash fits on iphone screen - home page: download box shadow 2012-04-11 Owen Stephens ~ - Use a couple of @-patterns in Patch.Depends - Rename getTagsRight - getUncovered, and move helpers into where block. - More tweaking of haddock of splitOnTag in Patch.Depends - Change name of infoAndDeps and add haddock to better express intent - Tweak/add more haddock to Patch.Depends - Reduce some duplication and tweak identifier names in Patch.Depends - Rename eatOne - unwrapOneTagged and extract common code in Patch.Depends - Tidy up and style changes for Exec - Indentation and line-wrapping in English - Add some Haddock and tweak some identifier names in Patch.Depends - Fixup a couple of occurences of with_partial_intersection in Patch.Depends - Resolve issue1921: return Nothing in splitOnTag if the tag isn't in the patchset - Tweak issue1921 test to check for graceful failure - Tweak a few identifiers and implementation of helpers for getTagsRight - Remove unused getPatchesInTag function from Patch.Depends - Rename and refactor simpleTag in Patch.Depends, to better express intent - A few more operator spacing tidy-ups in Patch.Depends - Accept issue1921: attempting to apply a patch bundle based on missing tag dies. - Tidy/style Patch.Depends 2012-05-11 Michael Hendricks ~ - Fix utf8 test for rollback --no-record default 2012-04-29 Florent Becker ~ - Tweak rollback help - Give feedback when no hunks are selected in rollback --no-record - Change rollback help to reflect --no-record as the default - Make rollback --no-record the default 2012-05-05 Yuriy Vostrikov ~ - Fix darcs diff handling of directory argument. 2012-05-04 Michael Hendricks ~ - Accept Bitcoin donations via CoinCard 2012-04-01 Florent Becker ~ - Make findUncommon and findCommonWithThem into findCommonAndUncommon - More precise witnesses for with_partial_intersection - in with_partial_intersection, we only need to assert that the middle witness (wA) is correct 2012-03-30 Owen Stephens ~ - Add failing test for issue2047. 2012-05-02 Simon Michael ~ - home page: browsable
[darcs-users] darcs weekly news #95
# News and discussions 1. Darcs 2.8 was released: - http://lists.osuosl.org/pipermail/darcs-users/2012-April/026493.html 2. Report of the seventh hacking sprint was put online: - http://blog.darcs.net/2012/04/darcs-hacking-sprint-7-report.html 3. BSRK Aditya was accepted as a Summer of Code student to work on the patch index optimization: - http://www.google-melange.com/gsoc/project/google/gsoc2012/bsrkaditya/28002 - http://wiki.darcs.net/GSoC/2012-PatchIndex # Issues resolved in the last week (4) issue1166 Guillaume Hoffmann ~ - --unified flag for record, amend-record, revert and unrevert - http://bugs.darcs.net/issue1166 issue2065 Owen Stephens ~ - filter and give warning for any malformed boring regexs. - http://bugs.darcs.net/issue2065 issue2120 Adam Wolk ~ - Darcs fails to invoke an editor under MS Windows - http://bugs.darcs.net/issue2120 issue2139 Florent Becker ~ - detect what to do when using darcs mv into/onto a directory - http://bugs.darcs.net/issue2139 # Patches applied in the last week (111) 2012-04-24 Ganesh Sittampalam ~ - update source link for 2.8 release 2012-04-05 Owen Stephens ~ - Layout/Tidy of Patch.Bundle 2012-04-05 Ganesh Sittampalam ~ - remove stale Tested-with entry from cabal file 2012-04-01 Owen Stephens ~ - Haddock HashedRepo, and make a few fairly trivial refactorings - Extract duplicated code in readInventoryPrivate, in HashedRepo - Extract out the use of pristine: literal into an identifier - Refactor listInventories function in HashedRepo - Extract string literals for identifiers for inventories/pristine - hlint suggestions to HashedRepo - Change fmap - $ in HashedRepo - Layout/tidy of Repository/HashedRepo - Fix Patch.Set export list indentation 2012-04-06 Michael Hendricks ~ - Implement exponential backoff test strategy - Factor out function to build bisect strategy initial state - Factor out initial test run - Improve darcs test descriptive help - Correct typos in trackdown-bisect test comments - Consistent test strategy function naming - Clearer test strategy selection - Factor out Strategy type - Unify darcs test strategy type signatures - Use safeApply throughout Darcs.Commands.Test - Style and Haddock for Darcs.Commands.Test 2012-04-17 Owen Stephens ~ - Parse RepoFormat properties once, storing as an ADT, rather than a ByteString. - More tidying of Repository.Format - Tidy Repository.Format - Tidy Repository.Merge 2012-04-01 Ganesh Sittampalam ~ - move URL.Curl to other-modules to avoid problems when curl isn't available - add a comment - drop unnecessary superclasses from MyEq (PatchInfoAnd p) - drop unnecessary call to joinPatches in Darcs.Resolution - drop unnecessary call to joinPatches in Darcs.Repository.Merge 2012-03-31 Eric Kow ~ - Replace CPP witness macros with plain Haskell in Darcs.SelectChanges.hs - Replace CPP witness macros with plain Haskell in Darcs.PrintPatch.hs - Replace witness CPP macros with plain Haskell in Darcs.Commands.AmendRecord 2012-04-01 Ganesh Sittampalam ~ - fix name shadowing warning in Darcs.SelectChanges 2012-03-16 Guillaume Hoffmann ~ - dirty fix for compile error in SelectChanges 2012-03-09 Andreas Brandt ~ - Tidy up wspfr 2012-03-08 Guillaume Hoffmann ~ - resolve issue1166 --unified flag for record, amend-record, revert and unrevert - change help of --unified to refer to changes in place of patches 2012-04-22 Florent Becker ~ - Update current version in homepage 2012-04-20 Michael Hendricks ~ - Patch 788 bundle 2012-04-01 Ganesh Sittampalam ~ - import constructors of C types to deal with a GHC change - fix deprecation about using unsafePerformIO from Foreign - add missing type signatures - remove unused imports in Darcs.Commands.Revert - remove unused imports in Darcs.Ssh - remove unused import in Darcs.Global - remove unused import in Darcs.Patch.ApplyMonad - fix name shadowing warnings in src/Darcs/Patch/ApplyMonad - remove unused import in Darcs.Patch.Choices - fix deprecated syntax in Darcs.Patch.Choices - remove unusued imports in Darcs.Patch.Patchy.Instances - remove redundant exports from Darcs.Patch.Prim - remove unusued imports from Darcs.Patch.Prim.V1.Show - remove unused import from Darcs.Patch.Prim.V1.Show - add missing type signature in Darcs.Patch.Split - switch from block/unblock to mask - change from deprecated use of GHC.Handle.fdToHandle - remove an no-longer-needed pragma - remove unused import in Darcs.Patch.RepoPatch - remove unused imports in Darcs.Patch.V1.Viewing - remove unused imports in Darcs.Patch.V2.Non - remove unused imports in Darcs.Patch.Viewing
[darcs-users] darcs weekly news #94
in Darcs.Commands.ShowRepo - Replace witness CPP macros with plain Haskell in Darcs.Commands.ShowIndex - Replace witness CPP macros with plain Haskell in Darcs.Commands.ShowFiles - Replace witness CPP macros with plain Haskell in Darcs.Commands.Send - Replace witness CPP macros with plain Haskell in Darcs.Commands.Rollback - Replace witness CPP macros with plain Haskell in Darcs.Commands.Revert - Replace witness CPP macros with plain Haskell in Darcs.Commands.Replace - Replace witness CPP macros with plain Haskell in Darcs.Commands.Repair - Replace witness CPP macros with plain Haskell in Darcs.Commands.Remove - Replace witness CPP macros with plain Haskell in Darcs.Commands.Record - Replace witness CPP macros with plain Haskell in Darcs.Commands.Put - Replace witness CPP macros with plain Haskell in Darcs.Commands.Push - Replace witness CPP macros with plain Haskell in Darcs.Commands.Pull - Replace witness CPP macros with plain Haskell in Darcs.Commands.Optimize - Replace witness CPP macros with plain Haskell in Darcs.Commands.MarkConflicts - Replace witness CPP macros with plain Haskell in Darcs.Commands.Get - Replace witness CPP macros with plain Haskell in Darcs.Commands.GZCRCs - Replace witness CPP macros with plain Haskell in Darcs.Commands.Convert - Replace witness CPP macros with plain Haskell in Darcs.Commands.Changes - Replace witness CPP macros with plain Haskell in Darcs.Commands.Apply - Replace witness CPP macros with plain Haskell in Darcs.Commands.Annotate - Replace witness CPP macros with plain Haskell in Darcs.Commands.Add - Replace witness CPP macros with plain Haskell in Darcs.Arguments - Replace witness CPP macros with plain Haskell in Darcs.Annotate - Replace witness CPP macros with plain Haskell in test_stub - Replace witness CPP macros with plain Haskell in Darcs.Test.Patch.WithState - Replace witness CPP macros with plain Haskell in Darcs.Test.Patch.WSub - Replace witness CPP macros with plain Haskell in Darcs.Test.Patch.V3Model - Replace witness CPP macros with plain Haskell in Darcs.Test.Patch.V1Model - Replace witness CPP macros with plain Haskell in Darcs.Test.Patch.Properties.V1Set2 - Replace witness CPP macros with plain Haskell in Darcs.Test.Patch.Properties.V1Set1 - Replace witness CPP macros with plain Haskell in Darcs.Test.Patch.Properties.Real - Replace witness CPP macros with plain Haskell in Darcs.Test.Patch.Properties.GenericUnwitnessed - Replace witness CPP macros with plain Haskell in Darcs.Test.Patch.Properties.Generic - Replace witness CPP macros with plain Haskell in Darcs.Test.Patch.Properties.Check - Replace witness CPP macros with plain Haskell in Darcs.Test.Patch.Examples.Set2Unwitnessed - Replace witness CPP macros with plain Haskell in Darcs.Test.Patch.Examples.Set1 - Replace witness CPP macros with plain Haskell in Darcs.Test.Patch.Arbitrary.Real - Replace witness CPP macros with plain Haskell in Darcs.Test.Patch.Arbitrary.PrimV3 - Replace witness CPP macros with plain Haskell in Darcs.Test.Patch.Arbitrary.PrimV1 - Replace witness CPP macros with plain Haskell in Darcs.Test.Patch.Arbitrary.PatchV1 - Replace witness CPP macros with plain Haskell in Darcs.Test.Patch.Arbitrary.Generic - Replace witness CPP macros with plain Haskell in Darcs.Test.Patch - Replace witness CPP macros with plain Haskell in Darcs.Test.Misc 2012-03-31 Simon Michael ~ - another fix for utf8.sh test, update to current rollback ui 2012-03-27 Michael Hendricks ~ - List conflicted files one per line 2012-03-24 Guillaume Hoffmann ~ - make darcs test more consistent - update manual for darcs test and repair --dry-run - make check an alias for repair --dry-run - add regression test to check warning message presence for darcs test - switch to test --trackdown and test --bisect - adapt testsuite to test --trackdown and test --bisect - adapt test suite to switch from darcs check to darcs test - introduce darcs test, doing the same as did check --test without repo check - Remove the function delimiters 2012-02-14 Will Langstroth ~ - Organize export list in Darcs.Patch - Haddock-friendly formatting for Darcs.Patch.Apply 2012-01-31 Owen Stephens ~ - Fix improper handling of FileNames that are prefixes-of, but not parents-of a target FileName. - Add current_name attribute to created_as in changes --xml on multiple files. - Resolve Issue2136: Correctly track renames of multiple files in Changes --xml. - Rename withFilePaths - withFileNames, since it operates on FileNames not FilePaths. - Replace applyToFilepaths with applyToFilePaths to match casing of FilePath - Add new helper function to determine if a given filename is the parentOrEqual of another
[darcs-users] darcs weekly news #93
News and discussions 1. The Shouthampton sprint will begins this Friday! More information on the wiki: * http://wiki.darcs.net/Sprints/2012-03 * http://lists.osuosl.org/pipermail/darcs-users/2012-February/026379.html 2. Haskell.org is participating to this year's Google Summer of Code, and is going to act as an umbrella organization for Darcs: * http://www.haskell.org/pipermail/haskell-cafe/2012-March/100247.html Issues resolved in the last week (2) issue1228 Michael Hendricks * Add --pause-for-gui to diff, pull and apply * http://bugs.darcs.net/issue1228 issue2145 Guillaume Hoffmann * enable j key in amend-record * http://bugs.darcs.net/issue2145 Patches applied in the last week (20) - 2012-01-22 Owen Stephens - Fix amend-unrecord test, broken by last-regrets prompt 2012-03-15 Michael Hendricks - Resolve issue1228: Add --pause-for-gui to diff, pull and apply - Style updates for Darcs.Commands.{Apply,Diff,Pull} - Function for asking the user to press Enter 2012-03-19 Guillaume Hoffmann - rollback fix for issue2135 that does not solve the unknown lines in annotate 2012-01-28 Will Langstroth - Readability changes to Darcs.Annotate 2012-01-22 Owen Stephens - Resolve issue2135: Don't keep trying to annotate a file, after processing the patch that added the file. 2012-01-26 Will Langstroth - Add Haddock header to Darcs.Annotate 2012-03-09 Eric Kow - Skip ssh tests in cabal test. 2012-03-09 Guillaume Hoffmann - resolve issue2145 enable j key in amend-record 2012-03-23 Michael Hendricks - Remove comment addressed in patch/issue discussion - Document 'l' option at the last regrets prompt 2012-03-22 Guillaume Hoffmann - change o key to g in select-changes UI for consistency with vim and less 2011-12-29 Eric Kow - Last regrets spelling and capitalisation tweak. - Update tests to work with last regrets prompt. 2011-06-15 Florent Becker - Don't ask confirmation if there are no things to select in textSelect - remove double confirmation in revert - Add a last question after all patches have been selected to confirm the whole selection 2012-02-19 Andreas Brandt - Accept-issue1522: trailing slashes confuse darcs 2012-03-01 Owen Stephens - Tidy up and Haddock Non. Rename some functions in Non and correspondingn use-sites in Real ___ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users