On 8/22/13 2:15 PM, Laszlo Kishalmi wrote: > I'd propose a -b [--branch] option or extend the meaning of "^" sign for > those commands which can work with URL-s. Extending ˇ would mean > that when used as ^/ it means repository root and using it as ^[branch] > then it would refer to a branch. > > How would it work: > > Let's imagine the following repository layout: > /project1/trunk > /project1/trunk/dir1/dir2/dir3/fileA > /project1/branches/branchA > /project1/branches/branchA/dir1/dir2/dir3/fileA > /project1/branches/branchB > /project1/branches/branchB/dir1/dir2/dir3/fileA > /project1/tags/tag1 > /project1/tags/tag2 > > Use Case 1: > We are in the WC root of checked out trunk and would like merge > branchA back. > svn merge -b branchA > svn merge ^branchA
I'm not sure how I see that this is so much better than just doing: svn merge ^/project1/branches/branchA I type these sort of things routinely with our own Subversion repo as: ^/subversion/trunk and ^/subversion/branches/1.8.x on a regular basis. If you want to make quickly aliases why not just use the variable support of your shell? E.G. with bash: branchA=^/project1/branches/branchA svn merge $branchA Or heck you can make it even shorter to type: bA=^/project1/branches/branchA svn merge $bA I used to do shell variables a lot before ^/ was added. That's back when we were hosted on subversion.tigris.org and we didn't have other projects in our repo and our trunk was a child of the root. With ^/ even with the subversion parent above our repo I just don't find myself using the variables. I'm sure you can probably even get your shell to be fancy and figure out what project you're working in and apply the proper root (you have access to this with svn info). Additionally I'm concerned that this just confuses the meaning for users of how ^/ works. I can already see the user complaints that Subversion merged the wrong thing for them because they forget -b. Let's just say that at this point I'm skeptical of the need for this.
