Rev 976: Updates to layout spec. in file:///data/jelmer/bzr-svn/layout/

Jelmer Vernooij jelmer at samba.org
Sun Mar 23 16:53:16 GMT 2008


At file:///data/jelmer/bzr-svn/layout/

------------------------------------------------------------
revno: 976
revision-id: jelmer at samba.org-20080323165315-fzjr7u2hxnkoqmj6
parent: jelmer at samba.org-20080322030540-jip3jh96fycgsxof
committer: Jelmer Vernooij <jelmer at samba.org>
branch nick: layout
timestamp: Sun 2008-03-23 17:53:15 +0100
message:
  Updates to layout spec.
modified:
  specs/layout.txt               layout.txt-20080203230450-3jog72dlme7x4su4-1
=== modified file 'specs/layout.txt'
--- a/specs/layout.txt	2008-03-22 03:05:40 +0000
+++ b/specs/layout.txt	2008-03-23 16:53:15 +0000
@@ -13,19 +13,18 @@
 When searching for revision ids, we need to search a limited set of paths in 
 the repository for branch properties.
 
-When importing a branch, we need to import the relevant tags. 
+When importing a branch, we need to import the relevant tags so we need 
+to know where to find them.
+
+In order to push right hand side history into Bazaar, it should be 
+possible to create new branches inside the repository automatically.
 
 Since there may be more than one project in a repository and it can be 
 very inefficient to have to browse the full repository it will be useful 
 to be able to restrict the paths searched on a per-project basis.
 
-Proposal
---------
-In order to deal with this information, we need to keep a list of branches
-and tags per project.
-
 Storage
--------
+~~~~~~~
 It should be possible to specify the repository layout locally as the user 
 may only have read-only access to the repository. It should be possible to 
 set the layout globally as well, inside of the repository, so it is possible
@@ -34,11 +33,18 @@
 If repository layout is known, one should be guess - similar to the way 
 that is currently being done for branching schemes.
 
+Proposal
+--------
+In order to deal with this information, we need to keep a list of branches
+and tags per project.
+
 Backwards compatibility
 -----------------------
 Branching schemes should be derivable from the repository layout. 
 
 Implementation
 --------------
+A new class RepositoryLayout will be created that can manage a list of 
+branch paths, tags paths and locations to add new tags or branches.
 
 .. vim: ft=rest




More information about the bazaar-commits mailing list