Kurt Madsen wrote:
>Part of the problem is that some developers create log messages (via
>commit -m "my message") at the file level deep in the project tree. And,
>other developers create log messages at the top-level directory for a
>project.
>
>
Either I don't understand what you're saying here, or you misunderstand
how log messages work.
In Subversion, files don't have individual revisions; the entire
repository has revisions. A new revision of the repository might have
one change to one file, or many changes to many files. Log messages
apply only to repository revisions, not to files or projects.
When you type "svn log <TARGET>", it looks for all repository revisions
in which <TARGET> changed, and reports the log messages for those
revisions. There is no direct relationship between a log message and the
file(s) it applies to. So talking about log messages "at the file level"
or "at the top-level directory" doesn't make sense; they are all at the
repository level.
So, to find log messages for all changes between revision X and revision
Y, simply type "svn log -rX:Y <URL>", where <URL> indicates what you
want messages for. If you want log messages for every file changed in
the whole repository, make <URL> the root URL of your repository.
Throw in the -v (or --verbose) flag to see not only the log messages for
each revision, but also which files changed in each revision.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Sep 1 19:45:52 2004