[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [PATCH] truncate EDITOR_EOF_PREFIX with previous EOL

From: Olleg Samoylov <olleg_at_mipt.ru>
Date: 2005-07-22 00:52:32 CEST

> Greg Hudson <ghudson@MIT.EDU> writes:
>>in the ideal case, svn:log properties should be thought of as a series
>>of lines, and we should ensure that they are by requiring that they have
>>a final newline.

Is this standart of log messages? "svn commit --message" and "svn log"
don't support this. And svn or server don't guarantee this invariant.

kfogel@collab.net wrote:
> For Subversion's repository, how hard would it be to write a
> pre-commit script that takes the log msg from the txn, removes all
> leading and trailing blank lines and guarantees that the log message
> ends with a single newline, and writes it back to the txn before the
> commit? About fifteen minutes? Thirty? :-)
How hard apply a patch? About two minutes? One?

> Not that I've started this, but if someone did, would we be fine with
> it?

I can't undestand official position of subversion developers. Obviously
this is bug because svn don't work as expected. When I write 1 line
message to log, I expect 1 line message in log. Clear and simple.

They are several patches to fix. Ones fix "svn commit", others "svn
log". Based on two opinion must or not log messages always ended with EOL.

But all patches rejected and I advised to write hook script to fix this.
I can't undestand. Can anyone explain me?

Olleg Samoylov
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 22 00:51:18 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.