Le 5269 Septembre 1993, Stefan Reichör a tapoté: > Hi Daniel! > >> 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 have implemented a way to mark exactly one bookmark entry (via #) > This marked entry is considered for dvc-missing (it uses the local-tree data > field) > > Does this work for you?
Yes, this mark the bookmark entry, I would like to mark the partner entry instead. For now, I put the point on the partner entry and run dvc-missing or dvc-merge, it run the missing on the bookmark entry (the parent of the partner field) against the current partner. What I would like is to group all the DVC branches under a DVC 'topic' (like in Gnus topic). For now, my bookmarks look like this: dvc.dev Partner http://bzr.xsteve.at/dvc/ [Stephan Reichoer] Partner http://www-verimag.imag.fr/~moy/bzr/dvc/moy/ [Matthieu Moy] Partner http://mwolson.org/bzr/dvc/ [Michael W. Olson] Partner http://stephe-leake.org/dvc [Stephen Leake] Partner http://bazaar.launchpad.net/~toby-mi6/dvc/toby_allsopp [Toby Allsopp] CFengine.pkg Partner /home/dad/src/cfengine/cfengine.dev CFengine.trunk CFengine.dev Partner https://svn.iu.hio.no/projects/cfengine-2/trunk [Upstream] Partner /home/dad/src/cfengine/cfengine.pkg [Package management] CFengine_conf.work CFengine_conf.dev Partner /home/dad/conf/cfengine/cfengine_conf.work [Work] pam-pkcs11 Partner http://www.opensc-project.org/svn/pam_pkcs11/trunk [Upstream] dvc.cdbs Partner ~/src/emacs/dvc/dvc.dev/ You can see that dvc.cdbs is at the end of the buffer, which is not convenient. >> 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, > > This should work via # > >> - I create a branch in dvc/fixes/bugfix-<number> (this add the >> entry in the dvc bookmarks automatically ;-)), > > How do you like to create the dvc/fixes/bugfix-<number> branch? Well, with the point on a branch or marking a branch, I run dvc-branch and it ask me for a place where to put the branch. Grouping all the branches of a same project under a 'project root entry' can be usefull to add variables on that root, for example a 'repository path', this directory contains all the branches I have, it's initialized by 'bzr init-repo /patch/to/the/directory'. This variable could be proposed during a dvc-branch call. > I see no dvc/fixes repository in your tree above - is it missing? It was just an example. I hope I'm clear in my explanation. I'll try to resume my request: is it possible to get the layout we want in the dvc-bookmarks ? With topics and subtopics, each containing branches or partners. My dream is: when I create a new topic in my dvc-bookmarks, this create a new directory on my filesystem, at the right place. Then I can branch whatever branch I want in a directory under the new directory. I'll try to look at the Gnus Group management to look if I can reproduce something like this. 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
