Max Bowsher wrote:
> No problem, we are discussing it now :-)
>
> The thing is, simple though it may seem, there still things that need to
> be discussed, and filed into the issue - we intend our issue tracker to
> be a kind of developer to-do list, which means that where enhancements
> are concerned, we want to have matters of design qualified enough so
> that it's possible to tell how big a job an issue is, and what code it
> is expected to touch.
>
> In this case, "svn info" is, at present, a tool for printing info from
> the WC .svn dir nicely.
>
> Most (but not all) of the information also is valid about a URL, so we
> might be able to get away with overloading the info command with 2
> different features, depending on whether it is given a path or URL - but
> a possibly contentious UI issue like this requires discussion, and
> consensus!
Speaking as the person who originally implemented 'svn info', I'd love
to see it work on URLs, so if someone finds the necesarry tuits then go
for it. It will, of course, be considerably more complex than the
current WC only implentation though. There will have to be a lot of
jumping through hoops to retrieve all the needed info, whereas in the WC
case it's all nicely there for us.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Sep 25 15:29:23 2004