This is for an automated bidirectional svn<->darcs gateway built on top of
Tailor.

On Thu, Jan 26, 2006 at 03:44:52AM +0000, Zooko wrote:
> This is for an automated bidirectional svn<->darcs gateway built on top of
> Tailor.
> 
> title: I wish for "darcs obliterate --all".

Are you serious?! This just seems like the definition of a joke command
that couldn't possibly be useful!  :) I'm sure there's got to be some use,
but I just can't see it.

How would this differ from "rm -rf *; darcs init"?

I guess it'd maintain _darcs/prefs/{defaults,email,motd} and the choice of
pristine cache type, and would leave any uncontrolled files in the working
directory... but I don't see how that combination would be helpful.

(but it certainly would be a humorous command...)
-- 
David Roundy
http://www.darcs.net

> Are you serious?! This just seems like the definition of a joke command
> that couldn't possibly be useful!  :) I'm sure there's got to be some use,
> but I just can't see it.
> 
> How would this differ from "rm -rf *; darcs init"?

Sorry I wasn't clear!  I meant to use it with patch selection arguments.  I
currently have a script for two-way sync between svn and darcs, and at one step
it does this:

yes | darcs oblit --help --patch="\[r[1-9][0-9]*\].*\[from darcs\]$"

It would be nicer (and perhaps a tad safer) if I could write:

darcs oblit --all --help --patch="\[r[1-9][0-9]*\].*\[from darcs\]$"

This is analogous to the way "pull --all --patch=REGEX" means "pull all patches
that match" rather than "pull all patches".

Regards,

Zooko

I just sent a patch for this in to the list.

David

fixed in 1.0.9