Michael Olson <[EMAIL PROTECTED]> writes: > Stefan Reichör <[EMAIL PROTECTED]> > writes: > >> Then I use gnus to apply the patch. That functionality is not yet >> ready for bzr. But I will implement it, if Michael does not need that >> kind of functionality. > > It would be useful to have, so I'll implement it unless you beat me to > it :^) . Should I make a bzr-gnus.el file for it? Also, should I try > to make the tla-specific keystrokes in the gnus keymap more generic? > (i.e. determine which backend we're currently using and call the > appropriate function)
Yes it would be desirable to determine the backend according to the mail content. Now there are two backends with gnus support: tla: - K t a: apply the patch - K t v: view the patch - K t l: read the log message body from the mail hg: - K t s: show the status buffer for this working directory - K t i: import the patch in hg So there is no unification yet. But it would be a nice thing to have! - Viewing is easy, since we send patches or bundles (both are text formats). - Extracting the log message should work the same way as in tla for patches. The log message is already part of the bundle so the extraction is not needed there. - Viewing the status of the working copy where the patch will be applied is a useful feature. - To apply a patch it would be useful to unify K t a and K t i. Stefan. _______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
