Daniel Dehennin <[EMAIL PROTECTED]> writes: > Le 5079 Septembre 1993, Matthieu Moy a tapoté: >> In this case, it doesn't seem to be a remote branch (the URL is >> file://..../). >> >> What command does DVC run to get this (end of the buffer you'll get >> with M-x dvc-open-internal-log-buffer RET)? > > Command: /usr/bin/bzr --no-aliases diff --revision revno\:222..revno\:223 > Directory: /home/nebu/src/emacs/dvc/dvc.dev/ > Date: jeu 02 aoû 2007 13:39:58 CEST > Related Buffer: *bzr-missing* > Output Buffer: *bzr-process*<12> > Error Buffer: *bzr-errors*<12> > Event: exited abnormally with code 3 > > I see that trying to see the log of a partner branch doesn't work: > > Command: /usr/bin/bzr --no-aliases log --revision 223 > Directory: /home/nebu/src/emacs/dvc/dvc.dev/ > Date: jeu 02 aoû 2007 13:42:02 CEST > Related Buffer: *temp* > Output Buffer: *bzr-process*<3> > Error Buffer: *bzr-errors*<3> > > There is no location spectified.
OK, that's a bug. DVC tries to access the revisions by providing their revision numbers, but it doesn't specify the location (and BTW, revision numbers really only make sense when associated to a location, the same revision can have different revision numbers in different locations, only the revision ID is unique). Unfortunately, that's non-trivial to fix, especially since bzr's support for diffing remote revisions seems broken (I wrote a patch that went into mainline allowing "bzr diff -r revno:42:http://whatever.com/bzr..revno:43:http://whatever.com/bzr";, but it seems broken now. There were a lot of other proposals for the same kind of things, but the developpers do not seem very interested). -- Matthieu _______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
