Mechanism for registering "mergeables" classes

[Jelmer Vernooij]

   affects bzr
   status confirmed
   importance wishlist

For bzr-git, I'd like to support being able to do "bzr merge
0001-git-am-style-patch.patch". In order to allow this, a probing
mechanism would be necessary in
bzrlib.bundle.read_mergeable_from_transport().

[John A Meinel (jameinel)]

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

Jelmer Vernooij wrote:
> Public bug reported:
>
> affects bzr
> status confirmed
> importance wishlist
>
> For bzr-git, I'd like to support being able to do "bzr merge
> 0001-git-am-style-patch.patch". In order to allow this, a probing
> mechanism would be necessary in
> bzrlib.bundle.read_mergeable_from_transport().
>
> ** Affects: bzr
> Importance: Wishlist
> Status: Confirmed
>

The bundle serializer already has a pluggable system for registering new
formats. Is that not sufficient? (It may not be flexible enough), but
there already is *some* support for this. It is just done at the
'bundle-reader' sort of level.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkrP6XYACgkQJdeBCYSNAANErwCZASGJIgFy4WfgSAtf3M4KMHgO
dFgAnR5C72qvO7/VCTqHrvOoyx3/EKDT
=iDkJ
-----END PGP SIGNATURE-----