Karl Fogel wrote:
>
> Blair Zajac <blair@orcaware.com> writes:
> > It seems that svn log should ideally be a local operation and not
> > one that connects to the svn server, for several reasons (I just
> > tailed my Apache access log and svn log had hits show up there).
>
> But why would one want to do this? That's a lot of data to store
> locally, and it can get out-of-date (since log messages can be changed
> after commit, and are not versioned). And the only way to see *new*
> log messages would still be to connect to the server...
If I'm working at the airport or away from a network connection, I would
still like to see the logs. Also, logs are probably not going to change
that much after a commit that the old information would be worthless. I
can always get the new logs when I'm reconnected.
Finally, regarding disk space, if we are already storing a copy of a
revision in the .svn directories, then storing a log doesn't seem like
a lot of extra space, maybe 1K at most in the text.
>
> > 1) This would be needed for disconnected operation.
>
> We don't support full disconnected operation. We support certain very
> common operations locally ("show me my local changes") but that's all.
As cvs does this currently and I would like svn to replace our cvs
repositories, is this something we can add?
>
> > 2) It's faster.
>
> No faster than running "svn log" once and saving it to a file, when
> you need it. You can spend the time up front, or you can spend it on
> demand. :-)
Well, I'd rather have svn make my work easy than having to remember to
do that. If I forget to run svn log, then I'm screwed?
> > 4) Cvs does not need a network connection to do cvs log.
>
> CVS does contact the repository to do "cvs log", not sure what made
> you think it doesn't (?).
My bad. I ran a cvs log but didn't let it run to completion. It does
make a single connection to the cvs server.
Blair
--
Blair Zajac <blair@orcaware.com>
Web and OS performance plots - http://www.orcaware.com/orca/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:08 2006