On Thu 2002-10-31 at 14:27:03 -0600, Karl Fogel wrote:
> Benjamin Pflugmann <email@example.com> writes:
> > Sorry, if I am ignorant. But why does it require a path? I thought
> > revisions were global. So I only need a repository URL, not a path to
> > an entity, don't I?
> Yup, this is the confusion.
> By default, 'svn log' does not get log messages for the whole
> repository. It gets log messages for those revisions where a change
> was made under a certain path -- and if that path happens to be '/',
> then that's the same as asking for the logs for all revisions.
> But if that path is '/trunk', for example, then the log output won't
> show branch changes.
> Furthermore, the path is taken from the current directory in your
> working copy, if you don't specify some other path (or URL) as an
Thank you for answering. That's how I understood it already. Sorry
that I was not more explicit about that.
The original answer why the command (svn diff -rM:N) may give no
output was a technical description how it currently works. And I
wanted to know, why it works as it does.
What I meant was: Why does it *require* a path? Or in other words:
Why, when no path is given, does it implicitly take "." as path
instead of working on the repository per se? Is there some reason I do
not see (perhaps consistency with other commands), or is this simply
what seemed to make sense when it was first implemented? Or something
Received on Fri Nov 1 00:53:50 2002
- application/pgp-signature attachment: stored