On 08/28/2013 05:51 AM, Daniel Shahaf wrote:
Les Mikesell wrote on Fri, Aug 23, 2013 at 16:07:17 -0500:
On Thu, Aug 22, 2013 at 4:15 PM, Laszlo Kishalmi <lkisha...@ovi.com> 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
So how do you see this working where your branches have their own sub-levels:
/project1/branches/release/branchA
/project1/branches/qa/branchA
/project1/branches/dev/branchA
Who gets to use the shorthand?
^/project1/branches/(qa|dev|release)
would be shortened to
^qa/ ^dev/ ^release/.
(Or you could try to define something along the lines of
'^/.../branches/(qa|dev|release)/([^/+]) \1-\2', but I'm not sure of the
details right now)
Well in that case a meaningful shorthand would be to use ^qa/branchA,
^dev/branchA and ^release/branchA
I think it could be solved by any matcher either using prefix or rexexp,
or some simplified regexp one.
