[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Feature request: Vizualization of 'fsvs' properties.

From: mmm4m5m <mmm4m5m_at_gmail.com>
Date: Sat, 6 Sep 2008 11:35:16 -0700 (PDT)


> As you've probably noticed, TSVN uses a lot of custom properties (tsvn:
> bugtraq:, webviewer:, ...). When I first started implementing the
> features which required properties, I ask on the svn mailing list
> whether I could use svn: properties for those, since I wanted not just
> TSVN to have those features but other svn clients as well, and having
> those properties documented in the svn project would help.
> But that proposal wasn't accepted (I could say now that this wasn't my
> fault either).
> But instead of just using svn: properties anyway, I used other
> properties. That's the right way to do things.

To be honest, I was thinking that this is the case or there is
something like this...
Other way I just can't understand why this discussion is so hot hot
(Especially your comments Stefan, because they are not good or bad
about TortoiseSVN. Mostly they are bad about FSVS. Different project,
different developers, maybe you never try it, maybe you are not using

The reason for this hot discussion definitely is not because FSVS
badly need support from TortoiseSVN. And the answer could be very
simple: "Thank you! Very nice idea, but anyway TortoiseSVN do not plan
to implement such feature. (nice idea about custom columns or maybe
about using SVN for backup and/or version control for configuration

Also, from my point of view, there is huge difference between
'svn:bugtraq' and 'svn:mode', 'svn:time', 'svn:owner', 'svn:group'.
And that is the reason why you already got answer and the answer is
'NO'. (Sorry.)


To unsubscribe, e-mail: dev-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: dev-help_at_tortoisesvn.tigris.org
Received on 2008-09-06 20:44:53 CEST

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.