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

Re: Bug report - double-quotes in comment text appear to be interpreted as subversion commands

From: Andy Levy <andy.levy_at_gmail.com>
Date: Tue, 6 May 2008 07:08:16 -0400

On Tue, May 6, 2008 at 4:01 AM, Simon Large
<simon.tortoisesvn_at_googlemail.com> wrote:
> 2008/5/6 Nick Argall <nicka_at_zedmed.com.au>:
> >
> > Hello Subversion folks,
>
> >
> > The comment I tried to put against my revision was this:
> >
> > Added "NOT FOR RELEASE" screamers if FOR_RELEASE is not defined.
> >
> > This produced a Subversion commit error, telling me 'FOR not expected'. I
> > took a guess at what might be happening and replaced my comment with
> >
> > Added 'NOT FOR RELEASE' screamers if FOR_RELEASE is not defined.
> >
> > And all was well.
> >
> > I assume that not everybody out there is as clever as I am, so it might be
> > good for TortoiseSVN to scan comment text for " characters and throw up a
> > more meaningful error message if they are present. (It's possible that
> > there are other reserved characters to be wary of, but I don't know what
> > they are.)
> >
>
> Works for me. Do you have a pre-commit hook installed on the server
> which might be causing this?

I can almost guarantee it. I have the same issue with my pre-commit
hook. The batchfile interprets the double quotes literally instead of
treating them as data.

I think someone posted a better version of a batchfile which checks
for a commit message on the SVN Users list but I don't recall whether
it worked 100% or not.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-05-06 13:08:39 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.