CVS to Bazaar using cvsps-import

[Thomas Manson]

Ok, I've read a bit about the distributed concept.

Anyway, I still have this need :

I'm coding from multiple computer (ie same person behind muliple computer,
same project, working on the same 'logical branch') :

   - My home computer
   - My laptop
   - My company computer

Also, contributor may want to join.

I'd like to publish my commit on my linux server at home for the following
reason :

   - It's backed up (RAID 1 + backup export to a remote site)
   - If my last change is on my laptop, in a cvs way of thinking, I would do
   a commit so that my changes are available to my other machine.
   - have a place where official build are

Isn't it right to want to do that?

Thomas


On Mon, Oct 6, 2008 at 19:34, Paul LeoNerd Evans <leonerd at leonerd.org.uk>wrote:

> On Sat, 4 Oct 2008 16:26:57 +0200
> "Thomas Manson" <dev.mansonthomas at gmail.com> wrote:
>
> > So the output will be the actual bazaar repository?
>
> Yes.
>
> Coming from CVS, you're thinking about things in a bit the wrong way. CVS
> has a "repository" which is the entity that lives on the server, and
> various checkout directories, which live on the "clients". The repository
> itself has a location (the CVSROOT), and each project stored there has a
> name (the module name).
>
> bzr doesn't do this. A bzr "branch" stores a project's revision history,
> and a "checkout" is a place to work on the files stored there. There is
> no distinction between the identity of a branch, and a location you can
> access it from. The branch stored at e.g.
> http://bazaar.my.company/code/thing is just that - a bare location.
>
> Any way to access that branch (HTTP, local file, SFTP, ...) counts as a
> server. A "server" or "central repository" is a concept bzr itself
> doesn't have; it comes as a consequence of your procedures to access it.
> For example, you might have an SFTP server called repo.my.company.name
> which you declare as the server. This is an entirely human-level concept
> which bzr doesn't care about. The output here in your case, is a
> directory tree containing branches. This tree is suitable for use as such
> a server.
>
> --
> Paul "LeoNerd" Evans
>
> leonerd at leonerd.org.uk
> ICQ# 4135350       |  Registered Linux# 179460
> http://www.leonerd.org.uk/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20081006/44042d83/attachment-0001.htm