Hello,

I'll try to explain what I would like to see in DVC bookmarks to get
it better.

For now, I have en entry for each branch I use, each branch has its
own partner list, all theses partners list are almost the same.

I wonder if it possible to group all the branches related to a project
under a container, like the topics in Gnus, which can expand and
collapse.

The layout I use for DVC is like this:

dvc/
|-- devel                # My main development here
|-- mainline             # Stephan Reichoer branch
|-- branches             # My per-feature branches
|   |-- cdbs             # use CDBS for debian package
|   `-- package-maint    # dgnushack from Gnus with some modifications
|-- partners             # All the partners
|   |-- matthieu.moy
|   |-- michael.w.olson
|   |-- stephen.leake
|   `-- toby.allsopp
`-- releases             # When we'll have releases ;-)
    |-- 0
    |   `-- 9
    |       |-- 0
    |       |-- 1
    |       |-- 2
    |       `-- 3
    `-- 1
        `-- 0
            `-- 0

I'd like to reproduce this in my DVC bookmarks.

Instead of having a partner list per branch, I'd like to mark a
specific branch and then run dvc-missing, or dvc-merge on the branch I
want, for example:

  - I select dvc/partners/toby.allsopp,

  - I place the point on dvc/devel,

  - Then I run dvc-missing.

And what about managing branching in the DVC bookmarks, for example:

I think about having a dvc/fixes tree, when we will have releases, for
example:

  - I mark the release 0.9.2,

  - I create a branch in dvc/fixes/bugfix-<number> (this add the
    entry in the dvc bookmarks automatically ;-)),

  - Then I fix the problem and merge it in my dvc/devel branch.

bzr is simple to use on the command line, but I'd like to do quite
everything from Emacs.

Regards.
-- 
Daniel Dehennin
Récupérer ma clef GPG:
gpg --keyserver pgp.mit.edu --recv-keys 0x6A2540D1

_______________________________________________
Dvc-dev mailing list
[email protected]
https://mail.gna.org/listinfo/dvc-dev

Reply via email to