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

New "svn version" command [was: Subversion 1.2.0 Release Candidate 1 released.]

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: 2005-04-08 01:15:23 CEST

Branko Čibej wrote:
>> User-visible-changes:
>> * new 'svn version' subcommand, essentially same as --version (r10430)
>>
> Ohmigod... is that still in the code? I recall some strong objections
> against a "svn version" command, and sort of remember our deciding to
> rip it out again. What gives?

I thought it was here to stay because enough people had been adamant that it
was needed, for reasons something to do with reporting the version of the
server of a given repository, but it wasn't entirely clear and that doesn't
appear to have been done.

I don't like the idea of a "svn version" command that is like "svn --version".
  I think the subcommands should all be about versioning your files, and the
"--version" option was perfectly adequate for reporting the client's version.

In fact, the "version" subcommand appears to be a horrible hack, or at least to
have got mixed up in the horrible hack that currently implements "--help" and
"--version":

~/src/subversion> svn version http://svn.collab.net/
"http://svn.collab.net/": unknown command.

~/src/subversion> svn version add
add: Put files and directories under version control, scheduling
them for addition to repository. They will be added in next commit.
[...]

I'm inclined to propose reverting this unless somebody has a very good argument
to make.

- Julian

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 8 01:17:03 2005

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