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

Re: cmd line stuff (was: CVS update: ...)

From: Karl Fogel <kfogel_at_galois.collab.net>
Date: 2000-10-17 17:10:27 CEST

Greg Hudson <ghudson@MIT.EDU> writes:
> History and log are very different in CVS. The CVS history file keeps
> a list of operations on the repository and "cvs history" lets you look
> at it. I have no idea whether we plan to emulate this functionality.

I don't think we do.

CVS history records two kinds of operations: things that happened to
the repository, and things people did to their working copies (such as
checkouts, releases, etc).

The former information is all accessible directly from the svn
repository, no need for a history file anymore. Probably svn log will
show the information, if not, we can provide other commands (perhaps
called "history") to show it. But this should probably be
need-driven. I don't think it's a crucial part of the spec we're
writing at the moment.

The latter kind is not information svn repositories care about. We're
deliberately staying ignorant of what goes on in working copies,
because that's not the repository's business (and when there are
10,000 developers, it's not scalable for the repos to record that
stuff for all time).

> I actually believe that we should discard CVS's insistence that global
> options come before the command name and local options come after.
> From a user perspective, the difference between global and local
> options should merely be a documentation issue; global options are
> just "the options that most or all svn commands support".

Hmmm! That's an interesting idea.

I don't know what I think of it. Wow.
Received on Sat Oct 21 14:36:11 2006

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

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