Leo / bzr workflow + bzr plugin?

3 views
Skip to first unread message

gegard

unread,
Aug 2, 2008, 3:15:47 AM8/2/08
to leo-editor
New to Leo and only a day or two more experienced with bzr, I have not
quite sorted out an effective edit / save / test / repository workflow
with Leo and bzr. Assuming that this is a common workflow, would
somebody be prepared to summarize how they work, to help me (and
presumably many others!) improve my effectiveness?

Is anyone working on a bzr plugin for Leo - just to create a
repository and save revisions, perhaps pull out specific revisions -
no need to call any more of bzr, I don't think. Or would that just be
superfluous? I'm not yet at the state of considering doing this
myself, however trivial it may turn out to be.

Thanks.

Regards, Geoff

Edward K. Ream

unread,
Aug 2, 2008, 9:21:41 AM8/2/08
to leo-e...@googlegroups.com
On Sat, Aug 2, 2008 at 2:15 AM, gegard <geoff.g...@gmail.com> wrote:

New to Leo and only a day or two more experienced with bzr, I have not
quite sorted out an effective edit / save / test / repository workflow
with Leo and bzr. Assuming that this is a common workflow, would
somebody be prepared to summarize how they work, to help me (and
presumably many others!) improve my effectiveness?

This should be in the FAQ.  I've put it on the list.

In the meantime, here is one discussion of bzr from March:

http://groups.google.com/group/leo-editor/browse_thread/thread/85da5c574dc5fc0e/c5f4e2e34156bc3b?lnk=gst&q=workflow#c5f4e2e34156bc3b


Is anyone working on a bzr plugin for Leo - just to create a
repository and save revisions, perhaps pull out specific revisions -
no need to call any more of bzr, I don't think. Or would that just be
superfluous?

Using bzr is actually quite easy, once you get the hang of it.  I use exactly the same work flow on Linux and XP.  I open a console window, then issue bzr commands.  I use a 'b' alias for bzr, and I use bzr aliases to shorten typing.  Here are what I usually type:

bs  (short for bzr status)
b c -m "commit message" file or files (short for bzr commit <etc>)
b push
b log10 (prints last 10 log messages)
b recommit (short for b c -m "recommit after merge")
b up (short for b c -m "update aux files")
b merge

In practice, there isn't any need for something better.

HTH.

Edward

Edward K. Ream

unread,
Aug 2, 2008, 4:30:40 PM8/2/08
to leo-editor


On Aug 2, 8:21 am, "Edward K. Ream" <edream...@gmail.com> wrote:
> On Sat, Aug 2, 2008 at 2:15 AM, gegard <geoff.gardi...@gmail.com> wrote:
>
> > New to Leo and only a day or two more experienced with bzr, I have not
> > quite sorted out an effective edit / save / test / repository workflow
> > with Leo and bzr. Assuming that this is a common workflow, would
> > somebody be prepared to summarize how they work, to help me (and
> > presumably many others!) improve my effectiveness?
>
> This should be in the FAQ.

Actually, it is the first item of the FAQ:

http://webpages.charter.net/edreamleo/FAQ.html#how-do-i-use-bzr-to-get-the-latest-sources-from-leo-s-launchpad-site

Edward

gegard

unread,
Aug 6, 2008, 12:41:14 PM8/6/08
to leo-editor


On 2 août, 22:30, "Edward K. Ream" <edream...@gmail.com> wrote:
> On Aug 2, 8:21 am, "Edward K. Ream" <edream...@gmail.com> wrote:
...
> Actually, it is the first item of the FAQ:
>
> http://webpages.charter.net/edreamleo/FAQ.html#how-do-i-use-bzr-to-ge...

Thank you: I was thinking of projects other than Leo itself, but
realize that this is directly applicable, now.

All the best,
Geoff
Reply all
Reply to author
Forward
0 new messages