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

RE: "svn log -v" vs. "svnlook changed"

From: Ray Johnson <Rayj_at_ingenio.com>
Date: 2004-09-21 10:09:13 CEST

Uh - that's kind of funny... If you read the thread, the issue was that
"svnlook changed" returns *better* information than "svn log -v". That
is 1) you can tell if a change was to a property or a file & 2) you can
tell if a given path is a directory or a file. Svnlook tells you that
info "svn log -v" does not.

So clearly changing the name of the executable DOES change things! :)

Why is a schema change required to fix "svn log"? Just doesn't make a
lot of sense that svnlook can return this information correctly and svn
log -v can not - and your condescending dismissal certainly doesn't
clear it up...

Ray

-----Original Message-----
From: Max Bowsher [mailto:maxb@ukf.net]
Sent: Monday, September 20, 2004 6:06 PM
To: Ray Johnson
Cc: users@subversion.tigris.org
Subject: Re: "svn log -v" vs. "svnlook changed"

Ray Johnson wrote:
> Shoot - the bug indicates that because a schema change would be
> required this will not happen before 2.0.
>
> What about supporting URLs in the svnlook command? Is that something
> that could be done sooner?

That's something which will never happen.
svnlook is a dedicated local repository inspector.

Besides - if a schema change really is required, then simply changing
the name of the executable in which you put the code won't change that.

Max.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 21 10:09:51 2004

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

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