Re: svn commit emails

Timothee Besset <timo@qeradiant.com> writes:

> If you don't want to fix it, I will live with it (or switch to daily
> delivery / leave the list). I don't know about RFCs for mail formats, but
> using outrageously long Subject lines seems a pretty wacky use of email,
> whatever the reasons.

I ask this of the list-folk because I don't know the historical ways
in which commit messages of other projects look. What if instead of
subject lines like:

   svn commit: rev 262 - trunk/subversion/include trunk/subversion/libsvn_wc trunk/subversion/libsvn_ra_local trunk/subversion/libsvn_client trunk/subversion/svnlook trunk/subversion/mod_dav_svn trunk/subversion/clients/cmdline trunk/subversion/tests/libsvn_wc trunk/subversion/tests/libsvn_repos trunk/subversion/libsvn_repos trunk/subversion/libsvn_ra_dav

We did something more like:

   svn commit: rev 262 - in trunk/subversion: include libsvn_wc libsvn_ra_local libsvn_client svnlook mod_dav_svn clients/cmdline tests/libsvn_wc tests/libsvn_repos libsvn_repos libsvn_ra_dav

Basically, printing the longest common ancestor of all the changed
dirs, and the paths relative to that of those dirs.

?? Hm?

---------------------------------------------------------------------
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:45 2006