[merge] tags in repository

[Alexander Belchenko]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ilpo Nyyssönen пишет:
> Alexander Belchenko <bialix at ukr.net> writes:
> 
>> Martin Pool пишет:
>>> This adds tags stored in the repository, and visible across branches in
>>> that repository.  Adding a tag doesn't require a commit.  Tags are
>>> 'global' across projects so people should use them appropriately - eg
>>> putting the project name at the start of the tag like 'bzr-0.14'.  
>> I don't think the prefix it's a big problem. I'm personally tends to keep
>> in one shared repository only branches of one project and don't mix
>> projects.
> 
> Good for you. Not so good for someone who has put several projects to
> same repository. When that someone pushes or someone other pulls from
> him/her, all the other project tags go too. 
> 
> Essentially this forces to keep separate projects in separate
> repositories. I don't like it. For me it has been useful to be able to
> put several small projects under same directory and to have that
> directory as repository.
> 
> But maybe the benefits from this are so small that it is better to
> just branch without a repository. After all, small projects take so
> little space.

I use approach "one repo for one project" because:

1) I did not realise that branches inside shared repo could be created
in any subdirectory. I always think that branches in repo should
always be in first subdir, i.e.:

   repo/
       .bzr
       branch1/
           .bzr
       branch2/
           .bzr

And because of this my misunderstanding I try to keep different projects
separately to not mix branches of different projects.
Now (after I try cvsps-import pugin) I understand that I was wrong.

2) I'm unhappy with published projects of some bzr developers that
used shared repo on their web servers. E.g. Michael Ellerman
(and probably Aaron Bentley) store all his plugins in one shared repo.
This has one very bad side effect:
to pull one small project from big shared repo you need to read the whole
big fat repository knit indexes because bzr does not separate
unrelated branches and their revisions. It's only separate
knits for different files. Try to branch htmllog plugin and you'll
see what I mean.
For me this side effect is very very very unpleasant because I have poor
internet connection with low bandwidth.

So despite my misunderstanding of (1) I still think that disadvantages
of (2) is too big for me to put all eggs in one basket.

I strongly think that until bzr start explicitly separate different
projects in one shared repository it's better to keep different
projects separately.

When bzr will differentiate projects we could start to talk about
tags (or projects) namespaces. But right now it's too prematurely for me.

I don't want to put all eggs to one basket.

- --
Alexander
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFulhTzYr338mxwCURAunLAJ9OD1Q/Lg+qKVcW1PGAk6D9CPE+mQCdE0Ko
epoXQNBCjq0POmJyAFbSlRI=
=cgxV
-----END PGP SIGNATURE-----