[Fwd: Re: Relative path operations in bzr?]

[Martin Pool]

On 19/09/05, Andrew S. Townley 

> I agree that both have merit, I just hadn't read this in any of the
> tutorial or other documentation that I found on the wiki.  If it was
> there, I surely missed it.

I just added some explanation to the wiki.  If you can think of
anything else particularly unobvious please ask.

> On some of the other VCS pages, there's kind of a CVS user transition
> guide which I think would be useful as more people are trying things
> out.  I'm sure I'm not the only one assuming commands will be working a
> specific way.  Is there anyone out there that can do this already?

I think jblack is working on that kind of stuff, again on bazaar.canonical.com.

> Anyway, regarding basic use and other stuff the only thing I could use
> is tags.  I read the pages describing this, but for my CVS projects, I
> do nightly builds with tags like PROJECT_CMBUILD_### and then have
> release tags based off one of these like PROJECT_X_Y_Z.  This is
> probably not really applicable to anything but the "main" repository in
> a distributed system, but I'm curious how the intent of what I do with
> CVS can be done with bzr.

Again, just doing tags when we have them should cover that.  For
releases you'll want to create a branch directory for any pre- or
post-releases fixes that affect it.

> I *really* want to move to a distributed model and have been doing some
> research on monotone, darcs and bzr.  I've had too many times when
> rsyncing the CVS repository got me into trouble.  I'm not quite sure I
> agree with Linus about blowing away the working repository because I see
> that as a good way to lose revision history, but for something were you
> don't want to expose your "dirty laundry" in roll-up patches, I think it
> makes sense.

Well, I hope you enjoy bzr; it's younger than those two but making
fairly rapid progress.

-- 
Martin