[darcs-devel] old bug tracker

2006-01-14 Thread Eric Kow
Hi all, Shall we complete the transition to the new bug tracker, or at least inch closer to that goal? We could do this in a minimalistic fashion by 1. merging redundant tickets 2. resolving - old tickets (resolved == resolved-in-unstable?) - tickets that complain about RT -

Re: [darcs-devel] darcs patch: really suppress output in win32 exec

2006-01-14 Thread zooko
NT-based versions of Windows should support '', which includes Windows 2000. I would guess that it doesn't work under Win9x, but have no way to test. I've finally tried this redirection syntax in Windows 98. The redirection doesn't work Okay, thanks for the info. Could the

Re: [darcs-devel] How to submit patches that make your maintainer happy

2006-01-14 Thread Tommy Pettersson
To make it easier for those who want to help reviewing patches on the mailing list, I additionally recommend the use of --unified with darcs send. -- Tommy Pettersson [EMAIL PROTECTED] ___ darcs-devel mailing list darcs-devel@darcs.net

[darcs-devel] Repository.writePatch (issue80)

2006-01-14 Thread Jason Dagit
Hello, I was looking a issue80 and I discovered that Repository.writePatch reads the freshly written patch. This is a very expensive operation given the current patch format. So I started to wonder why it does that. This took me to DarcsRepo.write_patch which led me to

Re: [darcs-devel] darcs patch: Do not reread freshly written patch when recording.

2006-01-14 Thread Jason Dagit
Hmm..Sending this with darcs send --unified prevented darcs from letting me add a description (a setting which is set in my global darcs prefs). What I wanted to say is, I'm sending the patch for the email I just commented on. I tested the this change with the testsuite and everything

Re: [darcs-devel] darcs patch: document how to use p4merge as external merge tool

2006-01-14 Thread David Roundy
On Fri, Jan 13, 2006 at 06:57:17PM +0100, Juliusz Chroboczek wrote: +To use \verb!p4merge!, you would use +\begin{verbatim} +--external-merge 'p4merge %a %1 %2 %o' David, is that okay with you? It amounts to advertising for proprietary software. I'm fine with this. Given that the

Re: [darcs-devel] Repository.writePatch (issue80)

2006-01-14 Thread Ian Lynagh
On Sat, Jan 14, 2006 at 04:24:16AM -0800, Jason Dagit wrote: I was looking a issue80 and I discovered that Repository.writePatch reads the freshly written patch. This is a very expensive operation given the current patch format. So I started to wonder why it does that. To avoid the

Re: [darcs-devel] Repository.writePatch (issue80)

2006-01-14 Thread Ian Lynagh
On Sat, Jan 14, 2006 at 02:13:33PM +, Ian Lynagh wrote: darcs record -a ought to be a constant space operation. When recording new files, that is. If some exist it'll probably be O(f(largest files size)) for some function f determined by the diff algorithm. Thanks Ian

Re: [darcs-devel] darcs patch: fixes for testsuite

2006-01-14 Thread zooko
This is the only part that will appear in some UIs (notably web interfaces). It should be short, to the point, and understandable by itself. ``fixes for testsuite'' is okay, ``fix for issue79'' and ``Issue14 addendum'' are not. This doesn't make sense to me. fix for issue79 is more useful

Re: [darcs-devel] darcs patch: document how to use p4merge as external merge tool

2006-01-14 Thread Will
David Roundy [EMAIL PROTECTED] writes: On Fri, Jan 13, 2006 at 06:57:17PM +0100, Juliusz Chroboczek wrote: +To use \verb!p4merge!, you would use +\begin{verbatim} +--external-merge 'p4merge %a %1 %2 %o' David, is that okay with you? It amounts to advertising for proprietary software.

Re: [darcs-devel] darcs patch: Save email description file if a send fails

2006-01-14 Thread Zachary P. Landau
Sorry, I forgot that there were new patches in darcs-unstable. My previous patch fails with a conflict. Attached is a newer version that should work with the current repository. -- Zachary P. Landau [EMAIL PROTECTED] save-email-description-file-if-a-send-fails.dpatch Description: Binary data

[darcs-devel] darcs patch: Save email description file if a send fails (and 3 more)

2006-01-14 Thread Zachary P. Landau
Hello, I decided to go ahead and implement the --logfile and --delete-logfile support for send, as mentioned in my previous email. The first patch is just a resend of the one in that same previous email. Because these patches use a file for an email and not for a long description, I also am

Re: [darcs-devel] darcs patch: Save email description file if a send fails (and 3 more)

2006-01-14 Thread Tommy Pettersson
On Sat, Jan 14, 2006 at 05:12:40PM -0500, Zachary P. Landau wrote: Sat Jan 14 17:06:52 EST 2006 Zachary P. Landau [EMAIL PROTECTED] * Update tests to use --logfile instead of --file Without commenting on the change of option names, I think this patch name says the reverse of what's intended.

[darcs-devel] darcs patch: add a --diff-command flag (and 2 more)

2006-01-14 Thread Eric Kow
Sat Jan 14 23:57:32 CET 2006 Eric Kow [EMAIL PROTECTED] * add a --diff-command flag Sat Jan 14 23:59:01 CET 2006 Eric Kow [EMAIL PROTECTED] * refactor Resolution.run to use CommandLine.parseCmd Sun Jan 15 00:00:20 CET 2006 Eric Kow [EMAIL PROTECTED] * remove spurious '.' in doc New

[darcs-devel] darcs patch: Add support to make_email for optional h... (and 1 more)

2006-01-14 Thread Zachary P. Landau
Sat Jan 14 17:58:32 EST 2006 Zachary P. Landau [EMAIL PROTECTED] * Add support to make_email for optional headers Sat Jan 14 18:28:26 EST 2006 Zachary P. Landau [EMAIL PROTECTED] * Add --in-reply-to option to send command. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 New patches: [Add

Re: [darcs-devel] darcs patch: Save email description file if a send fails (and 3 more)

2006-01-14 Thread Zachary P. Landau
Hi, I realized while working on another patch that get_fileopt should really be in DarcsArguments.lhs and be named get_file, to be consistent with other options (like subject/get_subject) for example. Attached at the same patches but with an extra one to move this function. Sorry for not

Re: [darcs-devel] Repository.writePatch (issue80)

2006-01-14 Thread Jason Dagit
On Jan 14, 2006, at 12:22 PM, Jason Dagit wrote: On Jan 14, 2006, at 6:13 AM, Ian Lynagh wrote: On Sat, Jan 14, 2006 at 04:24:16AM -0800, Jason Dagit wrote: I was looking a issue80 and I discovered that Repository.writePatch reads the freshly written patch. This is a very expensive