I suspect that they're not actually gone, just the revision numbers change... yes, that sounds crazy, but if everyone starts with rev 505 and does some stuff and commits on after another you can't all get 506... even though on your local trunk, before the commit, that's what you'd seem to have.
View the output from `bzr log` and I think you'll find your commit messages in there, somewhere. With revision numbers like 504.3.1 Cheers -Terry --- On Fri, 6/6/08, TL <[EMAIL PROTECTED]> wrote: > From: TL <[EMAIL PROTECTED]> > Subject: Re: New FAQ entry re bzr > To: "leo-editor" <[email protected]> > Date: Friday, June 6, 2008, 6:08 PM > Using Terry's work flow with a local repository, I > committed the > leoSettings.leo file with a couple of vi emulator changes > as revision > 509. Later, with Edwards updates the leoSettings.leo > changes moved to > revision 511 and the revision description that I entered is > gone. > > Why is this happening? I think we need to find a work flow > that will > avoid this from happening. We're losing historical > documentation, > we're having to spend time to verify that changes > haven't been lost, > and confusion will occur if forum posts reference a change > in a > specific revision and then the change moves to a later > version. > > TL > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
