More flexible commits to bound branches

Sounds reasonable.

--
Martin

  subscribe <email address hidden>

that's what I current added to get a better error message

otherwise I get a 'NoneType' member .to_waeve doesn't have method ... error

=== modified file 'repository.py'
--- repository.py 2007-01-20 23:11:09 +0000
+++ repository.py 2007-01-29 13:47:06 +0000
@@ -391,6 +391,9 @@
         # TODO: More efficient implementation?
         return map(self.get_revision, revision_ids)

+ def fetch(self, source, revision_id=None, pb=None):
+ raise NotImplementedError(self.fetch)
+
     def add_revision(self, rev_id, rev, inv=None, config=None):
         raise NotImplementedError(self.add_revision)

On Thu, 2007-02-01 at 16:00 +0000, Stefan Metzmacher wrote:
> that's what I current added to get a better error message
>
> otherwise I get a 'NoneType' member .to_waeve doesn't have method ...
> error
The .to_weave() bit is actually a Bazaar bug. It shouldn't be trying to
use weaves when fetching changes between repositories that don't both
support weaves.

Cheers,

Jelmer
--
Jelmer Vernooij <email address hidden> - http://samba.org/~jelmer/

I think the reason for not doing this was because you have to create the commit on the remote machine (which means it would access remote knits for the old data, etc). Rather than creating it locally, and copying it across.

I understand the need for this as we get more mixed-format bindings. But hopefully we can find a solution that would allow mixed-formats, without penalizing same-formats with a remote commit.

Fixed in the 0.4 branch.

This has actually been fixed in upstream.

No longer needs a fix in bzr.