Comments on: DVCS Interoperability

By: Sb

Sb — Fri, 27 Jun 2008 19:01:57 +0000

You haven’t actually used Tailor, have you? Done any converting of code between VCSs? It’s always incomplete, buggy, and leaves garbage behind.

You might want to try it before suggesting it. I think you’ll see pretty quickly why it’s a bad idea!

If you’re talking about just “skinning” the git engine with bzr commands, that doesn’t work either. They’re very different under the hood; at best, you’ll create a mess of leaky abstractions and another baffling porceleain that nobody uses.

By: Interstellar Medium: the Free Software carnival » Blog Archive » Free Software carnival: 21 – 27 June 2008

Fri, 27 Jun 2008 15:59:14 +0000

[...] James Sharpe doesn’t think a choice needs to be made if the systems interoperate; [...]

By: James Sharpe

James Sharpe — Fri, 27 Jun 2008 11:52:18 +0000

meike: I don’t think that information stored is that much of an issue with DVCS, I don’t think I’ve ever come across a situation where the DVCS repository is bigger (and in most cases it is an order of magnitude smaller) than the svn repository from which it was converted.

By: meike

meike — Fri, 27 Jun 2008 11:23:57 +0000

Also think of the information stored, and size and such (which matters for the server).

By: bkor

bkor — Fri, 27 Jun 2008 05:54:56 +0000

blah: Why respond if you don’t have any arguments?

Regarding suggestion: I’d wish that suggestion was possible. But, I don’t think git-bzr will be as seamless as what e.g. Bzr-git would be able to provide. Just choosing Git on the server on that basis is IMO mad, given that I’d likely have to support it (while I don’t get it). Further, the likely method of Bzr would probably to call git commands directly, which IMO isn’t a nice integration method, plus you still have interoperability problems (Windows).

By: blah

blah — Fri, 27 Jun 2008 00:48:16 +0000

This is a really, really bad idea.