Thomas Moschny wrote: > On Monday 29 January 2007 16:11, Peter Dimov wrote: >> A main assumption in current implementation is that a revision is global >> to the whole repository. This is however not the case with bazaar and >> other distributed version control systems. > > Really? While I am not an bzr user, I thought that each branch in bzr has its > own revision numbering.
Actually each bzr revision has a GUID. The same revision could be in multiple branches under a different revno. Each bazaar branch does have its own numbering. > Thus supporting multiple locations (with independent > revision numbering) really means supporting multiple repositories (see > #2086), which, in the case of bzr, means supporting multiple branches, no? Standalone branches have their own repository. Bazaar also has the concept of a shared repository where multiple branches share the same revision store. With a shared repository when you branch within the repository you don't copy its revisions. You just refer to the ones in the shared store. If you branch to a standalone branch you need to copy all revisions. trac+bzr does support multiple repositories. I'm currently using a single one but I'll switch to the setup Aaron Bentley proposed me, namely giving each developer their own repository to avoid issues with umasks and access rights. > A more severe problem for vc backends other than svn is imho the fact that > the > vc api currently only supports a linear history, which means that (from > Trac's point of view) each revision can only have a single ancestor. This is > not the case e.g. for Monotone or Mercurial, and maybe others. bzr keeps a linear revision history. Thus revious_rev would always work. When you are at revision 50 and you merged another branch in, you commit revision 51. The previous revision of 51 is 50 but if you look at the changeset 51 you'll see it has two parent trees. You can browse to the other one from there. Regards, Peter --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
