Re: bzr repository ready?

[Eli Zaretskii]

> From: "Stephen J. Turnbull" <address@hidden>
> Cc: =?iso-8859-1?Q?=D3scar?= Fuentes <address@hidden>,
>     address@hidden
> Date: Sun, 22 Nov 2009 09:54:47 +0900
> 
> If you do this in git (and in git, I do!), it's painless, because you
> have only one workspace for all the small changes.  The branches are
> "colocated" in the same repository/workspace; they share a working
> tree.  That means that a rebuild is a simple `make', and it's
> incremental.  But Bazaar branches *cannot* at present be colocated;
> they *cannot* share a working tree.  That means that if you do a
> "bzr branch" for a one-line change, you have to do a "make bootstrap"
> to test.  EEEEEEeeeeeewwwwww.

For someone who comes from CVS (and centralized VCS in general), this
aspect is a no-brainer.

> You are.  *You* apparently don't miss having the VCS record your
> history as you go along, and that's OK.

As I wrote elsewhere, I do have history.

> For your use case, where you don't care about history, you're right;
> it's hard to beat CVS by very much.  Until a year from now, when
> Yidong comes to you and says, "what were you thinking when you wrote
> this code?!" and you are forced to say "I don't know"

I have full records of my design decisions and the history of changes.
So I will be able to answer such questions easily enough.  Not
everything in this world needs to be recorded in a VCS to be readily
available.  Especially if only one individual is working on a project.

> and you make the
> "obvious" fix and 6 months after *that* somebody inserts an Arabic
> obscenity into a letter to their mother because it's "I love you"
> spelled backwards....

A VCS is no panacea from bugs.

> Of course there are other ways to accomplish this kind of history-
> keeping, such as comments in the code and entries in the ChangeLog
> proper (lord, do I hate merging changelogs!)  Again, if that works for
> you, OK.  But I and many others find it useful to have the VCS manage
> that task, specifically because unlike a ChangeLog, it provides the
> exact patch that goes with the changelog.

I'm fine with that, I just said that I don't see how a VCS can "shine"
in my case.