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

Re: [PATCH] do not return random data in svn_swig_pl_info_receiver

From: Blair Zajac <blair_at_orcaware.com>
Date: Wed, 23 Jan 2008 07:26:14 -0800

Olaf Hering wrote:
> do not return random data in svn_swig_pl_info_receiver
>
> ---
> subversion/bindings/swig/perl/libsvn_swig_perl/swigutil_pl.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- a/subversion/bindings/swig/perl/libsvn_swig_perl/swigutil_pl.c
> +++ b/subversion/bindings/swig/perl/libsvn_swig_perl/swigutil_pl.c
> @@ -1155,7 +1155,7 @@ svn_error_t *svn_swig_pl_info_receiver(v
> swig_type_info *infoinfo = _SWIG_TYPE("svn_info_t *");
>
> if (!SvOK((SV *)baton))
> - return;
> + return SVN_NO_ERROR;
>
> svn_swig_pl_callback_thunk(CALL_SV, baton, &result, "sSS", path, info,
> infoinfo, pool, POOLINFO);
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: dev-help_at_subversion.tigris.org

Olaf,

Thanks for all the patches.

Two requests. In Thunderbird, all these patches are showing as replies to a
previous post, so please start a new thread for each patch:

http://subversion.tigris.org/mailing-list-guidelines.html#fresh-post

This will make it easier to follow up on each one.

Please supply a log message in our standard format so a committer can make the
commit easier.

http://subversion.tigris.org/hacking.html#log-messages

Regards,
Blair

-- 
Blair Zajac, Ph.D.
CTO, OrcaWare Technologies
<blair_at_orcaware.com>
Subversion training, consulting and support
http://www.orcaware.com/svn/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-01-23 16:26:35 CET

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.