You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Blair Zajac <bl...@orcaware.com> on 2002/02/15 01:51:46 UTC
Why is "svn log" a network operation
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).
1) This would be needed for disconnected operation.
2) It's faster.
3) If you are working on revision X and you do svn log, then you
get the log for X+N, which is not what you would expect.
4) Cvs does not need a network connection to do cvs log.
Best,
Blair
--
Blair Zajac <bl...@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
Re: Why is "svn log" a network operation
Posted by Sean Russell <se...@germane-software.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Friday 15 February 2002 10:42 am, Blair Zajac wrote:
> 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.
Logs can, and often do, if the developers are good about writing commit logs,
take up a huge amount of space.
> > 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?
CVS supports almost no disconnected operations. Log certainly isn't a
disconnected operation in CVS.
- --
|.. If trees screamed, would we be so cavalier about cutting them down?
<|> Maybe, if they screamed all the time, for no good reason.
/|\ --- Jack Handy
/|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE8bWM/P0KxygnleI8RAg2mAKCFZdhVZByaudYLCyZoVtGvpztXjACghf2r
NKOu9qMBIJ3iwvS/HTqo6Ws=
=t+oF
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Why is "svn log" a network operation
Posted by Blair Zajac <bl...@orcaware.com>.
Karl Fogel wrote:
> Huh? CVS supports disconnected operation even less than we do;
> certainly it can't show logs nor diffs unless it talks to the repos.
> I'd really like to know what you're seeing with CVS...
Actually, nothing that you're not seeing. Just that one netstat -an
test I ran to see if cvs made a connection led me to believe cvs had
more disconnected operations than it really does.
Blair
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Why is "svn log" a network operation
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
Blair Zajac <bl...@orcaware.com> writes:
> 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.
Run svn log and save the output. If you won't remember, just write a
wrapper script around svn to do it for you.
> > 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?
Huh? CVS supports disconnected operation even less than we do;
certainly it can't show logs nor diffs unless it talks to the repos.
I'd really like to know what you're seeing with CVS...
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Why is "svn log" a network operation
Posted by Blair Zajac <bl...@orcaware.com>.
Karl Fogel wrote:
>
> Blair Zajac <bl...@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 <bl...@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
Re: Why is "svn log" a network operation
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
Blair Zajac <bl...@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...
> 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.
> 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. :-)
> 3) If you are working on revision X and you do svn log, then you
> get the log for X+N, which is not what you would expect.
This has nothing to do with "svn log" being a local operation. It is
about changing the default behavior of "svn log" to show a more
restricted set of log messages. This might be good, depending on the
specific behavior.
The phrase "working on revision X" isn't very meaningful, in our
working copy's context. There are lots of revisions lying around (and
anyway, why would the most recent one be of more interest? I usually
want the full log on a file, for example.)
> 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 (?).
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Why is "svn log" a network operation
Posted by Daniel Berlin <da...@dberlin.org>.
On Thu, 14 Feb 2002, Blair Zajac wrote:
> 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).
>
> 1) This would be needed for disconnected operation.
> 2) It's faster.
That's because it's not *doing* anything.
> 3) If you are working on revision X and you do svn log, then you
> get the log for X+N, which is not what you would expect.
Actually, it is.
I except cvs log, without a revision number given to it, to give me the
log of all revisions, not just those i happen to have locally.
How else would you know if you want to update?
> 4) Cvs does not need a network connection to do cvs log.
On a remote repo?
Of course it does.
>
> Best,
> Blair
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org