Re: [viewvc-dev] viewvc.branches, viewvc.tags

C. Michael Pilato wrote:
> If by "work" you mean it won't croak, sure.  But for other definitions 
> of "work", I don't see how it can "regardless of the layout chosen".  
> The chosen layout is the very sticking point we're talking about -- 
> ignoring it doesn't make the problem go away.
I don't see how I ignored it :)

> Yes, in many repositories, you'll find /trunk, /tags, and /branches.  
> But in many others, you'll find something different (maybe different 
> projects in the root, with the trunk/tags/branches underneath them).
Yes, take for example the ASF
repos/asf/httpd/httpd/{branches,tags,trunk}
repos/asf/httpd/apreq/{branches,tags,trunk}

This is why the regex is not anchored with a '^' to start of line.

> This gets you the ability to treat changes to /trunk/foo and 
> /branches/my-branch/foo and /tags/foo as all related to the same item 
> (foo), just on different branches.  This brings parity with CVS, where 
> branches and tags are orthogonal to path-space.
Don't you get that either way?

i.e.
full path: /repos/asf/httpd/httpd/trunk/server/main.c
relative   server/main.c

Given dirs.dir, files.file, branches.branch... Its definitely faster/easier to
get that if you do it your way :)







-- 
------------------------------------------------------------------------
Philip M. Gollucci ([email protected])
o:703.549.2050x206
Senior System Admin - Riderway, Inc.
http://riderway.com / http://ridecharge.com
1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70  3F8C 75B8 8FFB DB9B 8C1C

Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]