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/26755 <pre>Say we have two related repositories 'head' and 'dev', actually both branches of the same project, i.e. 'dev' contains a number of patches that are not in 'head'. Now I want to see the end-result of all I have done in 'dev' compared to the 'head' branch, suitable for displaying in a graphical diff viewer such as kompare. I can do 'darcs push ../head --dry-run -v' but the result is not usable for external diff viewers. One possible solution would be an extra option for 'darcs diff' that selects another (related) repository such as indicated in the subject line of this message; so I could say darcs diff --related-repo=../head --diff-command="kompare %1 %2" A simple work-around is to (temporarily) tag the 'head' branch, pull the tag, and then 'darcs diff --from-tag'. This could also hint to a possible implementation of the feature. Cheers </pre> Benjamin Franksen 2013-05-21T10:48:18 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26753 <pre>Hi, I use utf-8 intensively: in console and in files it's my default encoding. With export DARCS_DONT_ESCAPE_EXTRA="áàéèíïóúüñÁÀÉÈÍÏÓÒÚÚÑ", export DARCS_DONT_ESCAPE_ISPRINT=1 or export DARCS_DONT_ESCAPE_8BIT=1 there is no problem for displaying files and diff changes when I run "darcs log --verbose", but the commit messages *don't* appear in UTF-8: $ darcs log --verbose Sun May 5 22:10:18 CEST 2013 xan&lt; at &gt;localhost * O no &lt;U+00E9&gt;s aix&lt;U+00ED&gt; hunk ./holamón.txt 1 -Hola què tal +Hola què tal. O no és així Sun May 5 22:05:19 CEST 2013 xan&lt; at &gt;localhost * Hola m&lt;U+00F3&gt;n addfile ./holamón.txt hunk ./holamón.txt 1 +Hola què tal How can I do for displaying the commit message in UTF-8? With 8BIT=1, I get: $ darcs log --verbose Sun May 5 22:10:18 CEST 2013 xan&lt; at &gt;localhost * O no �s aix hunk ./holamón.txt 1 -Hola què tal +Hola què tal. O no és així Sun May 5 22:05:19 CEST 2013 xan&lt; at &gt;localhost * Hola m�n addfile ./holamón.txt hunk ./holamón.txt 1 +Hola què tal My darcs versio</pre> xancorreu 2013-05-08T18:14:33 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26751 <pre>Hi there, This project sounds quite interesting and I'd like to write a proposal for it. Unfortunately I've only just seen the email about the darcs projects and the deadline is drawing close, and being unfamiliar with the code or the issue I have no idea where to start! I'd greatly appreciate more information on this project if any of the proposers or anyone in the know is reading! For some background, I'm a second year Computer science student at the University of Nottingham, and have used Haskell quite extensively in my degree thus far, with only more to come. Additionally I have a fair bit of experience with web applications. Cheers, Joe Nash _______________________________________________ darcs-users mailing list darcs-users&lt; at &gt;darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users </pre> Joe Nash 2013-05-01T16:44:53 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26748 <pre>Hi there, This project sounds quite interesting and I'd like to write a proposal for it. Unfortunately I've only just seen the email about the darcs projects and the deadline is drawing close, and being unfamiliar with the code or the issue I have no idea where to start! I'd greatly appreciate more information on this project if any of the proposers or anyone in the know is reading! For some background, I'm a second year Computer science student at the University of Nottingham, and have used Haskell quite extensively in my degree thus far, with only more to come. Additionally I have a fair bit of experience with web applications. Cheers, Joe Nash _______________________________________________ darcs-users mailing list darcs-users&lt; at &gt;darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users </pre> Joe Nash 2013-05-01T17:25:17 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26746 <pre>Hi Everyone This is something I have on my wish-list for longer than I can think. The idea is quite simple: a primitive change type that says "this sequence of lines moved from file X line N to file Y line M". Here, X and Y need not be different, i.e. a hunk move need not be between different files. To my knowledge no existing VCS has such a feature. There are two advantages I expect: (1) Moving code around is something I do regularly in the process of cleaning up my (or other's) code. Currently such changes are represented (e.g. when using record or whatsnew) as "remove these lines from file X line N (long block of code follows), add these lines to file Y line M (another long block of code follows)". The remove and insert changes need not even be adjacent to one another (they typically are not) and even if they are it is very hard for the human eye to spot small differences in a long stretch of text. So if the tool told me I have a move (or I could tell it that this is the case) then I could </pre> Ben Franksen 2013-04-30T23:51:42 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26745 <pre># 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: - &lt;http://darcs.net/GSoC&gt; 2. Sebastian Fischer implemented `darcs-history`, a program to be used as darcs posthook and that tracks patch movements inside of a repository: - &lt;http://lists.osuosl.org/pipermail/darcs-devel/2013-February/014754.html&gt; - &lt;http://lists.osuosl.org/pipermail/darcs-devel/2013-February/014898.html&gt; - &lt;http://www.informatik.uni-kiel.de/~sebf/darcs/darcs-history/README.html&gt; 3. Sebastian also suggested the possibility for darcs to easily split and merge patches that are depended upon: - &lt;http://lists.osuosl.org/pipermail/darcs-devel/2013-March/014965.html&gt; 4. Piyush P Kurur was also interested in some special kinds of deep `amend-record`: - &lt;http://lists.osuosl.org/pipermail/darcs-users/2013-March/026838.html&gt; # Issues resolved i</pre> Guillaume Hoffmann 2013-04-30T19:26:19 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26741 <pre>Hi everyone, I've uploaded my proposal for the GSoC, you can see it here: http://darcs.net/GSoC/2013-BetterRecord I would like to hear your comments. Marcio. _______________________________________________ darcs-users mailing list darcs-users&lt; at &gt;darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users </pre> Marcio Díaz 2013-04-29T04:26:07 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26740 <pre>Hi I've added a card[1] to the Darcs Hub wishlist on Trello (reset password feature). It contains a non-urgent implicit support request (it would be nice if the person I was trying to show a file to could log in before this feature is added). Is darcs-users the best place to raise feature requests etc for Darcs Hub, or should I be sending them somewhere else? Thanks Ash [1] https://trello.com/c/kew04adB </pre> Ash Moran 2013-04-28T20:03:56 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26739 <pre>Hi, darcs.net will participating in Google Summer of Code this year, under the umbrella of haskell.org - Google will be allocating 1 or 2 extra slots specifically for Darcs. Time is a little short, as we'd originally thought this arrangement was coming to an end: the student application deadline is 1900UTC on next Friday (May 3rd). Please see http://darcs.net/GSoC for ideas and what to do next if you are interested in participating. The most important thing is to get in touch with us informally asap. Many thanks to Guillaume Hoffmann both for making our initial application to be a separate organisation (which was unfortunately rejected), and then for talking to Google and establishing that our existing arrangement of having a dedicated slot under the haskell.org umbrella could continue. Cheers, Ganesh </pre> Ganesh Sittampalam 2013-04-25T06:00:25 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26734 <pre>Here is my impression of patch groups after reading through some of the mails in this list. A patch group of order (or type) n, abbreviated as PG(n), is inductively defined as 1. patch group of order 0 is the actual patches (hunks, addfile etc) 2. A patch group of order n+1 is a collection of patches of order n What about patch groups of higher order. PG(1): is a record (collection of PG(0)s or actual patches) PG(2): is a branch (a collection of PG(1)s or records). PG(3): is a repository (a collection of PG(2)s or branches). PG(4): is a team of repository, a group of people who work on a project. PG(n&gt;4): is something that gives me a headache. For all PG(n&gt;=0), one should be able to attach meta information. Operations ---------- Operations are restricted to certain level of the patch group. We have record level operations, branch level operations and may be repository level operations. PG(0): 1. Editing the working copy creates/deletes/modifies them 2. reverting deletes some of them </pre> Piyush P Kurur 2013-04-18T07:24:53 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26726 <pre>Dunno if anyone else has encountered this, but I see "cabal haddock" failing on darcs-2.8.4 when building with ghc-7.4.2 (Fedora 19 development). There are no clear errors messages output as far as I can tell but here is an example build failure: http://koji.fedoraproject.org/koji/taskinfo?taskID=5167231 (the build.log link is near the bottom) It builds fine for me with ghc-7.4.1 in Fedora 18. Should I open a bug in the issue tracker or is it a known problem? I also see it seems to have built successfully in Debian Experimental with ghc-7.4.2. Jens ps For now I have disabled building with haddock for the Fedora Rawhide build. </pre> Jens Petersen 2013-03-25T04:32:51 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26720 <pre>I have this one question on amend-record: Say we have a repository with patches p0 p1 p2 p3 p4. Then I realised that some thing is missing in p2 say. If p3 and p4 commutes with p2 then I could use ammend-record. However, I think there are natural use cases where actually p3 and p4 might not be commutable with p2 and one could like to safely ammend p2. Use case 1: I missed adding a new file when I recorded p2. As I understand it, if p denotes the diff between the recorded version and the working tree and if p commuted with both p3 and p4 (i.e. p3 p4 p can be commuted to p' p3' p4') then I should be allowed to ammend p2. The resulting repository would be p0 p1 p2' p3' p4'. (1) Is there some flaw that I overlooked ? (2) Is there a way of achieving this in darcs 2.8.1 ? (3) Is this feature implied by any other work in progress? Regards ppk </pre> Piyush P Kurur 2013-03-22T07:02:21 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26697 <pre># News and discussions 1. Darcs 2.8.4 was released. It supports GHC 7.6 and fixes `get --tag`: - &lt;http://lists.osuosl.org/pipermail/darcs-users/2013-February/026769.html&gt; 2. Here is the report from the 8th darcs hacking sprint: - &lt;http://blog.darcs.net/2013/02/darcs-hacking-sprint-8-report.html&gt; # Issues resolved in the last week (6) issue904 Nathaniel Filardo ~ - Fix record on Linux/FUSE/sshfs (fall back to sloppy locks automatically) - &lt;http://bugs.darcs.net/issue904&gt; issue2155 Dave Love ~ - Expurgate the non-functional annotate --xml-output option - &lt;http://bugs.darcs.net/issue2155&gt; issue2270 Sebastian Fischer ~ - fixed darcs changes -i --only-to-files - &lt;http://bugs.darcs.net/issue2270&gt; issue2277 Radoslav Dorcik ~ - rebase suspend and unsuspend supports --summary. - &lt;http://bugs.darcs.net/issue2277&gt; issue2282 Ganesh Sittampalam ~ - don't allow remote operations to copy the rebase patch - &lt;http://bugs.darcs.net/issue2282&gt; issue22</pre> Guillaume Hoffmann 2013-03-01T19:21:16 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26687 <pre>Hi I'm trying to upgrade darcs from 2.8.2 to 2.8.4 on OSX 10.8.2. I've somehow installed it through cabal (`which darcs` = "/Users/ashmoran/.cabal/bin/darcs"). I did a cabal update and that told me to upgrade cabal-install, but I got this error: % cabal install cabal-install Resolving dependencies... The build-tool has reset ENV. --env=std required. cabal: Error: some packages failed to install: Cabal-1.16.0.3 failed during the configure step. The exception was: ExitFailure 1 cabal-install-1.16.0.2 depends on Cabal-1.16.0.3 which failed to install. Does anybody know what this means? Sorry for the non-darcs related question, but the only reason I have cabal installed is to install darcs. I don't even remember how I installed Cabal now. I'm also a bit puzzled why cabal tells me darcs is not installed: % cabal list darcs * darcs Synopsis: a distributed, interactive, smart revision control system Default available version: 2.8.4 Installed versions</pre> Ash Moran 2013-02-27T21:41:34 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26681 <pre>Hi all A friend of mine (Martin, cc'd as we've been talking about this) has created a site Startups Manchester[1] which is designed to track the activity of people working on software startups. It works by listening to Git commits, either using a post-commit hook in the repository, or – for users of Git clients that don't run hooks – via a web hook from GitHub. I have a project I'd like to put on the site, but it's stored in darcs and hosted in a private repo on hub.darcs.net. What is the best way to sync a darcs patches into a git repo (the other way round being unnecessary)? I'd like syncing to work on-demand, rather than automatically. I amend-record patches quite often, so I'd like them to sync when I'm happy with them, rather than immediately. (If you're using the Git hook script that Startups Manchester generates, commits are broadcast immediately.) I'd almost certainly send commits to Startup Manchester the same time I pushed them to Darcs Hub. The DarcsGit page[2] says the project is effectiv</pre> Ash Moran 2013-02-25T16:39:13 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26678 <pre> Hi, I read the wikibook articles on patch theory: http://en.wikibooks.org/wiki/Understanding_Darcs/Patch_theory http://en.wikibooks.org/wiki/Understanding_Darcs/Patch_theory_and_conflicts and found it very enlighting! However, at first, I was misled by the introductory "Casual users be warned ..." since it let me read the second article before the first one, which does not work. I would very like to see the missing pieces to be filled in, e.g. on exponential merge time and conflict battles! I have still a question about the actual implementation: When I pull and push patches around then patches must be constantly commuted forth and back, right? Are they actually changed? If yes, how could darcs detect that patches are the same? Are they tagged with a key that identifies a patch even after a lot of commutation? Best, Henning </pre> Henning Thielemann 2013-02-24T09:14:55 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26672 <pre>Hello, I was looking for a way how to realize workflow with small development commits without cluttering the history at the same time. Some git users squash such development commits into a single one when a particular feature is finished. While this makes the history much clearer, a lot of important information is lost. (Moreover this method is a bit error prone, because such squashing must be done before pushing changes into a remote repository.) Ideally, one wants to have a clean history and at the same time some kind of access to the original detailed commits. (See also my SO question: Should I squash small, development commits into bigger ones? http://stackoverflow.com/q/14554110/1333025) Recently I've been told that mercurial is working on a concept that allows to safely "rewrite" history. As I understand it, it actually doesn't modify anything, it just adds specific information (markers) that signals that some commits should be invisible or visually replaced by something else. These markers are pr</pre> Petr Pudlák 2013-02-23T09:47:09 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26658 <pre>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. </pre> Guillaume Hoffmann 2013-02-21T13:49:16 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26651 <pre> The darcs team is pleased to announce the release of darcs 2.8.4: Changes ------- The main purpose of this release is to add support for GHC 7.6 (it's been tested with 7.6.1 and 7.6.2). The new 64 bit version of GHC for Windows is not yet supported; 64 bit is supported on other platforms as before. Various dependencies on hackage packages have also been bumped: base, network, unix, containers, bytestring, tar. The following problems have also been fixed: - Resolved issue2199 &lt;http://bugs.darcs.net/issue2199&gt; : get --tag can include extra patches - Removed the --xml-output option to annotate which has been non-functional for a while Downloading ----------- The easiest way to install darcs 2.8.4 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.4 Alternatively, you can download the tarball from http://darcs.net/</pre> Ganesh Sittampalam 2013-02-07T21:19:43 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26650 <pre># News and discussions 1. Confirmed: the next Hacking Sprint will be in IRILL, Paris on February 15, 16 and 17: - &lt;http://darcs.net/Sprints/2013-02&gt; - &lt;http://www.irill.org/&gt; 2. Darcs HEAD has been fixed to work with GHC 7.6 without encoding bugs, go ahead and try it! - &lt;http://bugs.darcs.net/issue2286&gt; - &lt;http://hub.darcs.net/darcs/darcs-screened/patch/20130118225947-81bb2&gt; # Issues resolved in the last week (4) issue2199 Ganesh Sittampalam ~ - getMatchingTag needs to commute for dirty tags - &lt;http://bugs.darcs.net/issue2199&gt; issue2236 Gian Piero Carrubba ~ - make 'n' an alias for 'q' in lastregret questions - &lt;http://bugs.darcs.net/issue2236&gt; issue2238 Gian Piero Carrubba ~ - let optsModifier remove all occurrences of LookForAdds - &lt;http://bugs.darcs.net/issue2238&gt; issue2247 Ganesh Sittampalam ~ - move patch index creation into the job running code - &lt;http://bugs.darcs.net/issue2247&gt; # Patches applied in the last week (45)</pre> Guillaume Hoffmann 2013-02-04T07:40:39 http://comments.gmane.org/gmane.comp.version-control.darcs.user/26649 <pre>Hi, I have a trouble with darcs and utf-8. I have the DONT_ESCAPE_* necessary things: ]$ export declare -x DARCS_DONT_ESCAPE_8BIT="1" declare -x DARCS_DONT_ESCAPE_ANYTHING="1" declare -x DARCS_DONT_ESCAPE_EXTRA="áéíóúñÁÉÍÓÚÑ" declare -x DARCS_DONT_ESCAPE_ISPRINT="1" declare -x HOME="/home/xan" declare -x LANG="ca_ES.UTF-8" declare -x LOGNAME="xan" declare -x OLDPWD="/mnt/magatzem/projectes/versionats" declare -x PATH="/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/bin/core_perl" declare -x PWD="/mnt/magatzem/projectes/versionats/qfer" declare -x SHELL="/bin/bash" declare -x SHLVL="1" declare -x SSH_CONNECTION="172.26.0.5 56554 172.26.0.3 22" declare -x SSH_TTY="/dev/pts/0" declare -x TERM="xterm" declare -x USER="xan" declare -x XDG_CACHE_HOME="/home/xan/.cache" declare -x XDG_CONFIG_DIRS="/etc/xdg" declare -x XDG_CONFIG_HOME="/home/xan/.config" declare -x XDG_DATA_DIRS="/usr/local/share/:/usr/share/" declare -x XDG_DATA_HOME="/home/xan/.local/share" but: $ darcs log Sun</pre> xancorreu 2013-02-03T19:09:20 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.version-control.darcs.user