[darcs-users] Re: Fixing a repo with duplicate patches

[Michael Sperber]

David Roundy <droundy at darcs.net> writes:

> On Tue, Dec 05, 2006 at 07:46:09AM +0100, Michael Sperber wrote:
>> David Roundy <droundy at darcs.net> writes:
>> > On Mon, Dec 04, 2006 at 07:47:27AM +0100, Michael Sperber wrote:
>> >> Generally, this worries me quite a bit: It appears tailor simply uses
>> >> the darcs command line to generate the repository.  Why does darcs
>> >> allow me to create a corrupt repo?  Is there any way to prevent this
>> >> from happening in the first place?
>> >
>> > It's been a wishlist request for a while (I believe).  We don't want to
>> > have a complete check by default, since that's an O(N) process where N is
>> > the length of the repository history (unless we did something tricky), but
>> > a check at the most recent patches would catch most such mistakes, and be
>> > cheap.  It just hasn't been anyone's top priority to add such a check.
>> 
>> So how do I fix the problem after the fact?
>
> You just have to regenerate the repository.  Darcs lost information when it
> was provided with two identical patch names with identical dates.

OK, so is there any way to trick tailor into not generating the
duplicate patch names?

-- 
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla