New semantics for split and join in bzr 2.0

[Jelmer Vernooij]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gioele Barabucci wrote:
> Hello,
> 
> I find the semantics of split and join difficult to understand. At least 
> their names are misleading to me.
> 
> From my POW, split should do what
> 
>   bzr fast-export $br | bzr fast-import-filter -i sub/dir/ | bzr fast-import
> 
> does. That is, split the subtree in an *independent* branch. I used this 
> myself and I see many use cases where this would be useful. When are the 
> current actions of split and join useful?
They're useful if you're splitting a new project out of an existing one.
E.g. if you have a library that you're splitting out of an existing
project to be a separate project.

> As 2.0 is approaching, it would be a good occasion to change the semantics 
> of these commands and move the old semantics to a separate plugin.
That approach is history-destroying, why would it be preferable over the
current approach?

Cheers,

Jelmer

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iJwEAQECAAYFAkoySPwACgkQDLQl4QYPZuVSiwP9F3iUSiyN2AEYw/Qn68huJUdr
6yUNTXPih2uSNNgkyXld8VCoZlKWHq8AroZT5o8rVFXoVWY7hLD9s7bwqi2iuSjV
vXri38E3n5HTpdM0ciUERXje8YVCMfSLOoQ+kYOJpAg7BO2HvrFEktL/Iji3WZlr
4/29RIrCUqyFEbFmM/g=
=Cv+4
-----END PGP SIGNATURE-----