On Wed, 2002-01-23 at 10:55, Justus Pendleton wrote:
> Greg Hudson writes:
> > Subversion associates exactly one log message
> > with a commit. I'm a little leery of it myself (it means that "svn log"
> > on a particular file will contain a lot of verbiage not directly related
> > to that file)
> I'm confused, why is a file involved in a commit if nothing about it has
> changed? If something about it has changed, why isn't that being mentioned
> in the log message?
Each log message in "svn log" will say something about the file being
logged, but it might say a lot of other stuff too. I'll give an
example.
Say I have two files, foo.c and bar.c. I completely rearchitect foo.c,
and as a result, some small detail about bar.c has to change (maybe, the
arguments in a call to a function from foo.c have to be reordered). The
log message for foo.c might be extensive, but when I view the log for
bar.c, all I really need to see is "function call changed to accomodate
new foo.c architecture," more or less. And maybe a pointer to the log
message for foo.c, if the system is rich enough to allow that.
As I said, we shouldn't be switching tracks on this point right now, but
it's something to keep in mind.
---------------------------------------------------------------------
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:36:58 2006