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

Re: svn commit: r30996 - in branches/gnome-keyring: . subversion/include subversion/libsvn_subr

From: Arfrever Frehtes Taifersar Arahesis <arfrever.fta_at_gmail.com>
Date: Wed, 7 May 2008 17:51:38 +0200

2008-05-05 22:26:15 epg_at_google.com napisał(a):
> arfrever_at_tigris.org writes:
>
> > Author: arfrever
> > Date: Sat May 3 06:53:15 2008
> > New Revision: 30996
> >
> > Log:
> > On the 'gnome-keyring' branch:
> > Miscellaneous improvements.
> >
> > * configure.ac: Rename the '--enable-gnome-keyring' option to
> >    '--with-gnome-keyring' and rewrite it to fix its behavior.
> >    Define SVN_GNOME_KEYRING_INCLUDES and SVN_GNOME_KEYRING_LIBS
> >    variables and mark them for substitution.
>
> This is the second time I've seen these weird characters where
> spaces should be in one of your log messages.
>
> 0 ~% svn log -r30996 http://svn.collab.net/repos/svn
> ------------------------------------------------------------------------
> r30996 | arfrever | 2008-05-03 06:53:15 -0700 (Sat, 03 May 2008) | 36 lines
>
> On the 'gnome-keyring' branch:
> Miscellaneous improvements.
>
> * configure.ac: Rename the '--enable-gnome-keyring' option to
> ?\194?\160 ?\194?\160'--with-gnome-keyring' and rewrite it to fix its behavior.
> ?\194?\160 ?\194?\160Define SVN_GNOME_KEYRING_INCLUDES and SVN_GNOME_KEYRING_LIBS
> ?\194?\160 ?\194?\160variables and mark them for substitution.
> [...]
>
> I could fix it again, but it would be nice if you could get to
> the root of the problem :)

I copied svn:log from the e-mail ('[PATCH] [gnome-keyring] Miscellaneous improvements')
stored in my e-mail client. Maybe it was somehow deformed...

-- 
Arfrever Frehtes Taifersar Arahesis

Received on 2008-05-07 17:55:25 CEST

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