Hi Vincent! It took a bit longer to get the needed infrastructure in place. Now I need your help to implement features you'd like to see.
> stefan> * The next thing is support to apply such a bundle > stefan> - either via merge > > In that case the needed command is: > cd <branch> > bzr merge <bundle> > > stefan> - or as a standalone branch in a specific location > > Either by: > > bzr init <branch> ; cd <branch> ; bzr pull <bundle> > > to create the branch or, if it exists: > > cd <branch> ; bzr pull --overwrite <bundle> K t a needs to detect, how the patch in a given article should be handled. dvc-gnus-article-apply-patch already knows some common mail formats. Today I have added the new configuration variable dvc-gnus-article-apply-patch-deciders. It is a list of functions that can analyze a mail message and return the detected patch type if any. e.g.: (setq dvc-gnus-article-apply-patch-deciders '(dvc-article-check-for-pull-bundle-in-branch)) (defun dvc-article-check-for-pull-bundle-in-branch () (message "checking...") 'bzr-pull-bundle-in-branch) Can you send me such a mail, that allows me to write a decider function and to implement the bzr-pull-bundle-in-branch functionality. >>From there, I'd hope to be able to do some "Monkey see, monkey > do" :D > > Vincent > > Off-topic: If dvc-diff could accept arguments when prefixed (C-u) > I'd be so delighted :) While I use 'dvc-diff' quite heavily, I > resort to: > > M-x shell-command-on-region <RET> bzr diff -rsubmit: <RET> M-x diff-mode > > far too often and this is really the most missed command in DVC > for my workflow. The following function should work now: (defun bzr-diff-against-submit () (interactive) (bzr-dvc-diff '(bzr (tag "submit:")))) Stefan. _______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
