[darcs-devel] can I get a patch for this bug for Debian?

2006-02-07 Thread Isaac Jones
Greetings, David suggested that I ask here about getting a patch for the bug mentioned here: http://thread.gmane.org/gmane.comp.version-control.darcs.user/9239 Some users feel this bug is pretty serious and I'd be happy to upload a patched version to Debian (against the 1.0.3 version). Can

[darcs-devel] [issue127] proposal: rename mv to move, rename remove to unadd

2006-02-07 Thread Zooko
New submission from Zooko [EMAIL PROTECTED]: Two problems: 1. Many users think that they need to use darcs remove to remove a file, much as one is required to use svn delete/rm/remove in Subversion. For example, see this thread:

[darcs-devel] Version Nummbers was patch: put deps.pl into the tools/ subdirectory

2006-02-07 Thread dagit
Quoting [EMAIL PROTECTED]: Interesting. Do you have any test cases? Or could this tool be used in any test cases to help stress darcs? No, but I use deps.pl personally to generate pretty graphs of my patch dependencies. I'm wondering if we should have a darcs-contrib repository.

Re: [darcs-devel] darcs patch: revert optimization for apply_list (and 1 more)

2006-02-07 Thread Tommy Pettersson
I meant to add a comment to this send, but I had to run off to work. These patches don't need to be applied to unstable right away. There's nothing wrong with them, they fix a bug with unpull by removing an optimization, but it can possibly be solved in a better way keeping the optimization. --

[darcs-devel] [issue128] apply_list fails on some hunks

2006-02-07 Thread Tommy Pettersson
New submission from Tommy Pettersson [EMAIL PROTECTED]: From: Aaron Kaplan There seems to be a bug in the way darcs inverts certain patches. Consider a file that begins as ---8- one two three ---8- and then is modified to look like ---8- three one ---8- If

[darcs-devel] getting new stable ready

2006-02-07 Thread Tommy Pettersson
I believe it is time to get a new stable release ready soon. I want issue67 and issue128 to be solved since they can cause corrupted repos. I also think issue48 should be addressed in some way, since it can have rather nasty effects and is not hard to exploit. issue67: Getting a tag giving