http://blog.gmane.org/gmane.comp.version-control.darcs.user hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.version-control.darcs.user/26406 <pre> Are there any conventions that users tend to gravitate towards? 1. Naming - with patches from a lot of people, do short names like : "Fixed the serialization of Foo" work? Do long names wrap a line telling exactly what you did work better? Or do you fall back on bug numbers? What if you can't fall back on issue numbers? Does pinpointing a patch by name or in some context get tricky? 2. Change granularity - do people tend to try to split a change up into parts, e.g. if a library and end-code are in the same repo, maybe patch the lib first and then the rest adding it as a dependency? 3. Merging patches. . . Does pollution of lots of tiny little changes ever become a problem, or something you address in practice? For example, say people all work on some related issue, put in lots of little fixes, then you're done - is it ever something where you want to just merge them all and have everyone work in terms of the amended repository? Or does the UI/history/etc. make it easy to find, or not find if you</pre> Matt Lamari 2012-05-23T00:36:59 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26404 <pre>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&lt;---- 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 ----&gt;8---- I've added </pre> Guillaume Hoffmann 2012-05-21T19:59:56 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26401 <pre> I think that the subject matter really warrants a handy paperback. </pre> Matt Lamari 2012-05-20T20:17:54 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26395 <pre>Hi, I began a project about six months ago as a single repository. I've now reached the point where I'd like to split out several files into a separate library, for use across multiple projects. Of course, I also want to preserve the history of these files in the new library repository. However, several of these patches include changes to other files (eg, in response to changes in module interfaces) and in order to pull all of the library-specific patches, I end up having to pull in a large number of additional patches. What I'd like to do is identify the relevant patches ("darcs changes file1 ... fileN") and pull modified versions of these patches that do not include any hunks that modify other files in the repository. I can't see a more efficient way of doing this than manually applying and recording individual hunks (using "darcs changes -v file1 ... fileN", or "darcs annotate --match XXX" and "darcs unrecord --last 1 --matches XXX"). It sounds as though the "amend-record on steroids" feature would be u</pre> Rob Moss 2012-05-17T10:53:20 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26392 <pre>Hi all, Just announcing another newcomer to the Darcs team. Simon Michael recently put a lot of work into revamping the Darcs homepage. As part of the team, he will be working primarily on the page and documentation, and hopefully over time, expand his areas of interest. Thanks, </pre> Eric Kow 2012-05-14T18:38:44 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26391 <pre># 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/tentativ</pre> Guillaume Hoffmann 2012-05-14T18:49:47 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26390 <pre>Hi, I've just released darcs 2.8.1 to hackage. The only change it incorporates is a bump to the dependency on mtl to allow it to build against the upcoming Haskell Platform. Therefore there's no need for any users to upgrade, nor is there any particular need for updated binaries except perhaps to avoid confusion about binaries being out of date. Cheers, Ganesh </pre> Ganesh Sittampalam 2012-05-14T18:17:21 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26387 <pre>Dear Hackage package maintainer, the release of the next haskell-platform is close, and it will most likely ship with mtl-2.1.1. Your package on Hackage does not allow building against this version, which makes it for your users and distribution packagers difficult to use the package. Please consider uploading a new version of your package with an extended mtl (and possibly transformers) dependency range. In most cases, no version changes are required. The list of affected packages¹ are: darcs diagrams-cairo ghc-events haskeline leksah ltk template vty haskelldb rss2irc The current plan for package versions in the platform can be seen at https://github.com/haskell/haskell-platform/blob/pre-release/haskell-platform.cabal Thanks, Joachim ¹ Only listing packages that are also shipped by Debian, not all affected packages on Hackage. </pre> Joachim Breitner 2012-05-13T11:02:24 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26386 <pre>Hi everyone, First, for those who have missed it, since darcs 2.8 all code testing features of darcs belong to the command "darcs test". Without flags, "darcs test" runs a test on the latest recorded state of the repository. However, flags --trackdown and --bisect look for the most recent recorded version passing a given test. We already know how --trackdown and --bisect work: --trackdown runs a test agains the last recorded version, then the last version minus one patch, then minus two patches... until finding a passing test. --bisect sort of does the same by jumping back and forth in the history by dichotomy. See http://wiki.darcs.net/Using/Trackdown for more information and unusually friendly drawings :-) So, the new interesting feature in HEAD is the exponential backoff strategy, implemented by Michael Hendricks. As explained by Michael himself on the bug tracker: ----8&lt;---- This patch series defines a new "darcs test" search strategy named --backoff. It's aimed at finding regressions which are c</pre> Guillaume Hoffmann 2012-05-12T23:03:17 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26378 <pre># 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 </pre> Guillaume Hoffmann 2012-04-27T19:48:22 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26377 <pre>Hi all, The darcs team is pleased to announce the release of darcs 2.8. Downloading ----------- The easiest way to install darcs 2.8 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.8 Alternatively, you can download the tarball from http://darcs.net/releases/darcs-2.8.0.tar.gz and build it by hand as explained in the README file. The 2.8 branch is also available as a darcs repository from http://darcs.net/releases/branch-2.8 Supported GHC versions and Unicode filenames. --------------------------------------------- Due to changes in ghc's handling of non-ASCII filenames, darcs 2.8 supports GHC versions 6.10.x, 6.12.x, 7.0.x, and 7.4.x. Version 7.2.x is also supported on Windows. On Unix systems, version 7.2.x is disabled by the cabal file, as using a darcs executable built using ghc 7.2.x could make the on-disk format of r</pre> Florent Becker 2012-04-22T18:34:56 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26367 <pre>Hi all, A bit over a week ago, we had the second half of the March Darcs hacking sprint, this time 6 of us in Southampton working on Darcs and Camp. Here's a report of the two sprints http://blog.darcs.net/2012/04/darcs-hacking-sprint-7-report.html Thanks, Eric PS: next up… HCAR! </pre> Eric Kow 2012-04-09T12:18:29 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26365 <pre>Hi all, The darcs team is pleased to announce the release of darcs 2.7.99.2, aka 2.8 rc 2, the second release candidate for darcs 2.8. Changes since 2.8 rc 1 ---------------------- - Fixed compile errors on GHC 6.12, and corrected the unintentional omission of 6.12 from the release announcement. - Fixed some warnings by pulling in any unconflicting patches to clean up warnings from mainline. Downloading ----------- The easiest way to install darcs 2.8 rc 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-beta-2.7.99.2 Alternatively, you can download the tarball from http://darcs.net/releases/darcs-2.7.99.2.tar.gz and build it by hand as explained in the README file. The 2.8 branch is also available as a darcs repository from http://darcs.net/releases/branch-2.8 Supported GHC versions and Unicode filenames. -------------</pre> Ganesh Sittampalam 2012-04-07T21:26:19 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26362 <pre>Hi all, I'm looking for some advice about the following darcs behaviour. I haven't found it reported in the issue tracker, but some issues seems similar enough so that I'm wondering if I should report it. $ darcs initialize $ touch foo bar $ darcs record -lam first Finished recording patch 'first' $ rm foo ; ln -s bar foo $ darcs whatsnew -ls R ./foo $ darcs record -am second No changes! Note that it would succeed (record the file removal) if I used either `darcs remove' or `darcs record -l'. Anyway this is only triggered by the presence of the symbolic link: $ rm foo $ darcs whatsnew -ls R ./foo $ darcs record -am second Finished recording patch 'second' What really hurts is the case in which the link addresses a not-existent file: $ touch foo $ darcs record -lam third Finished recording patch 'third' $ rm foo ; ln -s qux foo $ darcs whatsnew -ls darcs: /home/gpiero/tmp/darcs/repo/foo: openBinaryFile: does not exist (No such file or directory) $ darcs record -am fourth darcs: /home/gpiero/tmp/dar</pre> Gian Piero Carrubba 2012-04-05T22:11:44 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26357 <pre># News and discussions 1. The Southampton sprint is over! We'll put together a blog report soon. 2. Florent and Ganesh prepared a release candidate of Darcs 2.8, try it! - http://lists.osuosl.org/pipermail/darcs-users/2012-April/026445.html - http://lists.osuosl.org/pipermail/darcs-users/2012-April/026448.html 3. What would be the next big feature of Darcs 2.10? Ganesh proposed rebase, and Michael already provided feedback about this feature: - http://lists.osuosl.org/pipermail/darcs-users/2012-April/026443.html - http://lists.osuosl.org/pipermail/darcs-users/2012-April/026455.html 4. Eric asked what would be a nice mission statement for Darcs. A few propositions have been made so far: - http://lists.osuosl.org/pipermail/darcs-users/2012-March/026433.html # Issues resolved in the last week (3) issue2125 Owen Stephens ~ - only warn about forcing replaces, when a force is required. - http://bugs.darcs.net/issue2125 issue2136 Owen Stephens ~ - Corr</pre> Guillaume Hoffmann 2012-04-04T17:37:20 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26339 <pre>I've been playing with the rebase branch for the last couple weeks. Here's a lengthy brain dump. If you're interested in more explanation for any particular point, let me know. - suspend and unsuspend - have proven very useful - would be good building blocks for branch, rebase and stash plugins - should be top-level commands like record/unrecord, pull/unpull, revert/unrevert - are too low level to satisfactorily solve the deep amend problem for users - need a way to list suspended patches (darcs changes --suspended?) - pull - should be "darcs pull --suspend-conflicts" - even better would be "darcs pull --conflicts={mark,allow,disallow,skip,suspend-ours,suspend-theirs}" - suspending conflicted patches might offer more pleasant conflict resolution, one offender at a time - obliterate - should be "darcs obliterate --suspended"? - reify, inject - I don't understand the purpose of these commands - should their</pre> Michael Hendricks 2012-04-02T16:09:24 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26336 <pre>Hi all, Just a quick reminder that the Google Summer of Code is upon us. The deadline is coming up pretty quickly (Fri 6 April), so best get in touch if you want feedback on your proposals! http://www.google-melange.com/gsoc/events/google/gsoc2012 Thanks, </pre> Eric Kow 2012-04-01T16:09:22 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26329 <pre>Hi all, The darcs team is pleased to announce the release of darcs 2.7.99.1, aka 2.8 rc 1, the first release candidate for darcs 2.8. Downloading ----------- The easiest way to install darcs 2.8 rc 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.7.99.1 Alternatively, you can download the tarball from http://darcs.net/releases/darcs-2.7.99.1.tar.gz and build it by hand as explained in the README file. The 2.8 branch is also available as a darcs repository from http://darcs.net/releases/branch-2.8 Supported GHC versions and Unicode filenames. --------------------------------------------- Due to changes in ghc's handling of non-ASCII filenames, darcs 2.8rc1 supports GHC versions 6.10.x, 7.0.x, and 7.4.x. Version 7.2.x is also supported on Windows. On Unix systems, version 7.2.x is disabled by the cabal file, as using a dar</pre> Florent Becker 2012-04-01T09:46:09 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26327 <pre>Hi, I'm thinking about merging rebase into HEAD, for release in 2.10 (there'll be lots of conflicts so I would actually rebase the code). There would still need to be significant work on it and its UI, and if we don't manage to get it ready in time we could ship 2.10 with it disabled-by-default. However I think it is time to open it up for wider testing and feedback, and create some pressure to actually get it out. Any thoughts/objections? Cheers, Ganesh </pre> Ganesh Sittampalam 2012-04-01T08:35:33 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26326 <pre>Hi all, Just a heads-up for anybody who edits the wiki: We've switched from reStructuredText to Markdown (using Pandoc for our auto-conversion). http://wiki.darcs.net Hopefully any breakage this has caused will be easy to fix. This switch is entirely motivated by network effects. These days, Markdown usage is so widespread (off the top of my head, GitHub, Reddit, StackOverflow...), and enough people are familiar with it that it'd be a bit silly to ask people to have to learn two lightweight text formats just to make a little change to the wiki. Thanks much to Trent, Mark and others who have pushed for our usage of reStructuredText. If recall correctly, 1. When Trent was serving as doc manager, he advocated a separation of the user manual from the code (done now, thanks to Guillaume), and a switch from TeX to RST 2. When we switched from MoinMoin to Gitit, I decided to go with RST to avoid having two text formats within the community. 3. Now I'm going to assume that the arguments made 4 years ago in</pre> Eric Kow 2012-03-31T17:16:04 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26320 <pre>Imagine that I have patches A and B. B depends on A. I discover that A's patch name and long comment have a major typo. Unfortunately, "darcs amend-record --edit-long-comment -p A" won't work. B's dependency prevents A from being commuted to the front even though changing A's metadata won't affect B at all. I want an option letting me change A's metadata regardless of the dependencies. Would such an option be useful to others? What should it be called? darcs amend-record --none --edit-long-comment darcs amend-record --metadata-only --edit-long-comment I'm partial to --none since it's the opposite of --all. Ideally, amend-record would prompt for changes before prompting for which patch to amend. That way, if the user selects no changes Darcs can skip dependency analysis when presenting patches. Would changing the prompt order harm your favorite use cases? </pre> Michael Hendricks 2012-03-30T22:34:39 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.version-control.darcs.user