#73: Add documentation for branches/tags/trunk SVN assumptions
---------------------------+------------------------------------------------
Reporter: elegant_dice | Owner: lele
Type: enhancement | Status: new
Priority: minor | Milestone: VersionOne
Component: tailor | Version: 0.9
Resolution: | Keywords:
---------------------------+------------------------------------------------
Comment (by elegant_dice):
Ok that makes sense. I personally don't need the branches and tags, and
I'd suggest to not enhance tailor in this regard since there are
apparently several 'standard' ways to structure your SVN tree, so whatever
you implement will probably not work for 60% of users who need the
feature.
An additional (hopefully easy) question: since Tailor will work its way
back up the paths to check for the true repository root, is there any
difference in doing:
{{{
repository = svn://some.server/svn
module = /productA/trunk/
}}}
compared to:
{{{
repository = svn://some.server/svn/productA/trunk/
module = /
}}}
?
--
Ticket URL: <http://progetti.arstecnica.it/tailor/ticket/73#comment:4>
Tailor <http://progetti.arstecnica.it/tailor>
An inter-VCs changeset exchanger_______________________________________________
Tailor mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/tailor
