Branching scheme documentation needs improvement
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar Subversion Plugin |
Won't Fix
|
Low
|
Unassigned |
Bug Description
My svn repository is laid out like this:
trunk/project1
trunk/project2
branches/
branches/
branches/
branches/
branches/
branches/
When I first used bzr-svn, I told it to pull from $SVNREPOS/
Also: This is a per-user configuration variable. So, even if I do find out that there is a branching-scheme I could manually change to in the configuration file, every user would also have to make this same modification to their configuration file. That's not really usable.
Changed in bzr-svn: | |
importance: | Undecided → Low |
status: | New → Triaged |
Changed in bzr-svn: | |
milestone: | none → 0.4.5 |
Changed in bzr-svn: | |
milestone: | 0.4.5 → none |
Am Donnerstag, den 16.08.2007, 20:56 +0000 schrieb James Y Knight: project1/ mytestbranch/ project1 project1/ mytestbranch/ project2 project1/ releases/ 1.0/project1 project1/ releases/ 1.0/project2 project2/ whateverbranch/ project1 project2/ whateverbranch/ project2 trunk/project1. Now, when I did this, it chose a branching trunk/project1" (as shown in subversion. conf). So, now it refuses to pull down any other schemes" and choose a different branching scheme --set', for example:
> My svn repository is laid out like this:
> trunk/project1
> trunk/project2
> branches/
> branches/
> branches/
> branches/
> branches/
> branches/
>
> When I first used bzr-svn, I told it to pull from
> $SVNREPOS/
> scheme of "single-
> ~/.bazaar/
> projects or even other branches of the same project. It recommended that
> I type "bzr help svn-branching-
> scheme, but this didn't help me, as there are only two options listed
> there: "trunk", for the /trunk/* layout, and "none" for no branches,
> just one branch at the root.
You can also list your branches by running 'bzr svn-branching-
bzr.dev svn-branching- scheme --set svn://svn. samba.org/ smb-build/
and then enter something like:
trunk/* project1/ mytestbranch/ * project1/ releases/ */* project2/ */*
branches/
branches/
branches/
> Also: This is a per-user configuration variable. So, even if I do find scheme' command).
> out that there is a branching-scheme I could manually change to in the
> configuration file, every user would also have to make this same
> modification to their configuration file. That's not really usable.
This variable can be also be set on the repository (see the 'bzr
svn-branching-
Cheers,
Jelmer
-- samba.org/ ~jelmer/
Jelmer Vernooij <email address hidden> - http://
Jabber: <email address hidden>