"Dan Lipsitt" <[EMAIL PROTECTED]> writes:
> However, there are several
> things that I used to be able to do with dvc/tla that seem to be
> missing from dvc/bzr.
Yes.
The situation is:
* I'm almost the only contributor to DVC-bzr
* Lack of time, motivation, ...
* bzr's command-line is not perfect, but really useable. So, the need
for an Emacs mode is not as strong as it was with tla/baz.
* I'm indeed thinking of migrating to another VCS (hg? git?), thus
moderating my efforts on bzr.
> - Bookmarks seem to be Arch-specific.
There's a draft of a dvc-bookmarks facility, but not really usefull.
> - Partners are gone. I know that bzr stores at least the source of the
> last pull. Does it record other repos? Is there a way that dvc can
> track this otherwise? Maybe bookmarks could serve this purpose
> (something like bzr-{merge,missing}-from-bookmark).
You can maintain a shared repository containing a mirror of each of
your partner's branches. For example, I have
~/emacs-lisp/dvc -> shared repo
~/emacs-lisp/upstream -> mirror of Stefan's branch
~/emacs-lisp/moy -> where I hack.
I can
$ cd ~/emacs-lisp/dvc/upstream/
$ bzr pull
$ cd ../moy/
$ bzr merge ../upstream
or, with recent bzr,
$ cd ~/emacs-lisp/dvc/moy
$ bzr pull -d ../upstream
$ bzr merge ../upstream
> - Can't merge/cherrypick from bzr-missing screen.
AFAIK, bzr's cherrypicking is still really weak (bzr doesn't record
the merge, so further merges will be problematic).
> - Can't jump to conflicts from bzr-status screen.
That's clearly missing.
> There are also instances where dvc assumes that I am using tla. I
> sometimes get an error saying "not an arch managed tree" when I am in
> a bzr-managed directory.
It happens, and it clearly is a bug. Most of the time, instances of
this bug are quickly fixed, so you're welcome to report them.
> I will try to collect these as they come up. Lastly, the
> documentation at http://download.gna.org/dvc/docs/dvc-snapshot.html
> only covers tla.
Yup. We're too lazy to work actively on the code, and even more lazy
to write a good manual :-(.
--
Matthieu
_______________________________________________
Dvc-dev mailing list
[email protected]
https://mail.gna.org/listinfo/dvc-dev
