>>>>> Btw: I don't want to crush all your arguments and tell you to quit
>>>>> complaining, it's just that I don't have that much experience with
>>>>> tagging used in company procedures etc. The scenarios I can come up
>>>>> with
>>>>> all seem to work in subversion. So I have to have some examples
>>>>> before
>>>>> I
>>>>> am able to see what subversion lacks. (And what subversion doesn't
>>>>> quite
>>>>> lack, but still is very hard to accomplish.)
>>>> Make a program that lists all tags for a project (e.g. given the URL
>>>> of
>>>> the 'trunk').
>>> svn list <trunk-url>/../tags/
>>
>> No, this will not work if you have layed out the project with /trunk,
>> /tags and /branches in the root of the repository. The program cannot
>> know
>> your intentions without some meta-information.
>
> Your program can assume (or try first) the standard layout.
"assume"?? I am trying to find a solution in which Subversion "knows". Why
do you not want to find such a solution?
I was asked to give an example of a feature Subversion is lacking, and
gave one. You seem to agree on that, using phrases like "assume" and "try
first".
> Your program can also store meta information in a svn property.
This is what I am proposing, only that Subversion should manage the
properties. You put the burden of the special property handling on every
client, when it may be implemented once in Subversion.
Håkon Hallingstad
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 10 10:10:43 2006