[PATCH] convert/bzr: handle Bazaar timestamps correctly (issue1652)

[Martin Geisler]

Greg Ward <greg-hg at gerg.ca> writes:

> On Fri, May 8, 2009 at 4:45 AM, Martin Geisler <mg at lazybytes.net> wrote:
>> Ideally we should make Bazaar use a fixed time like we do for the
>> Mercurial tests --- I'm looking at the Bazaar code now to see if that is
>> possible.
>
> Or include tarballs of the Bazaar repositories to convert in the test
> suite.  It has several advantages:
>   * less dependence on variation in behaviour across bzr versions
>   * could test conversion from the multitude of Bazaar storage formats
> (although arguably, it's their job to make sure their API works
> consistently ;-)
>   * tests go faster
>
> And the obvious disadvantages of:
>   * test suite gets a bit bigger (but not much: repos used for testing
> conversion are usually small)
>   * we don't find out when changes in bzr break assumptions in
> Mercurial (or in its tests)
>
> IMHO this would be an even bigger win for testing CVS conversion,
> since the format of "cvs log" and the output of "cvs ci" and "cvs add"
> vary unpredictably.
>
> If this has been discussed before and shot down, let me know...

I just noticed that there is a tests/svn folder which holds a number of
Subversion repository dumps along with scripts for creating them.

So Bazaar wouldn't be the first convert source to ship with such
ready-made repositories.

-- 
Martin Geisler

VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multiparty Computation) to Python. See: http://viff.dk/.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://selenic.com/pipermail/mercurial-devel/attachments/20090519/f29e48e6/attachment.pgp