jerenkrantz@tigris.org writes:
> Author: jerenkrantz
> Revision: 13838
> Property Name: svn:log
>
> New Property Value:
> Merge CHANGES from the trunk and update dist.sh (in progress).
When we merge changes from one line to another, we usually give the
revision numbers (or revision number range) that was merged. In this
case it would probably be okay just to say "Bring CHANGES up-to-date
with trunk master copy" or something like that, as long as it's clear
exactly what's going on.
Regarding the dist.sh portion of the log message... uh, WTF, if I may
be so bold? :-) It ought to say *something* indicating the nature of
the changes. And especially if changes are "in progress", then the
commit should say what the final goal is, and how much progress has
been made toward that. For example, in the way r13832 and r13833 do.
As it happens, these dist.sh changes turn out to be a bit
controversial. Ben Reser has already brought up the -api vs -apri
thing, and other points, on the dev@ list, so I won't. Given that
controversy, it's probably just as well that the changes were
committed on the branch, but ordinarily trunk would (I think?) be a
better place for dist.sh maintenance (i.e., trunk for the master
change, then port it over to whatever release branches need it).
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 3 01:02:49 2005