LOC of different version control systems

[Alexander Belchenko]

Giorgos Keramidas пишет:
> On Mon, 01 Dec 2008 21:00:56 +0200, Alexander Belchenko <bialix at ukr.net> wrote:
>> Also Bazaar supports more concepts, more features/workflows and tows
>> support for numerous old repo formats. I think this explains its
>> codebase size.
> 
> Can you elaborate a bit on the `more workflows' part?  I've been seeing
> that mentioned here and there, that but I am not sure I understand what
> it means for the average ${VCS} user.

I don't know what it means: "for the average ${VCS} user". Can you explain, please?

I can explain only what I'm using everyday.

You can use bzr branches as standalone branches (this is typical scenario for hg, yes?).
You can use bzr branch on the some sort of server (smart or dumb) as master branch
and then do checkout on local machine. Your checkout could be almost the same as
regular branch, but when you do commit or pull all new revisions should go to master
branch first (otherwise you need use --local command-line option). Also bzr supports
lightweight checkouts -- it's roughly the same like checkouts in CVS, when you have
only working copy on your local disk without history, all branch history is accessible
via master branch (it could be on the server or local).

Also bzr supports work with many dumb servers (http is readonly, ftp, sftp is writable).
This is much slower than using smart server like bzr+ssh, but sometimes it's very useful.

As you understand I did not mention the same features both hg and bzr has.

This does not mean of course that all users will use everything, but I'm using all mentioned
above and it helps me in my work. But I'm probably not typical "average ${VCS} user", because
I was bzr windows maintainer during several years.