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

Re: CHANGEs File for Subversion 1.6 - Questions - API Change

From: Hyrum K. Wright <hyrum_wright_at_mail.utexas.edu>
Date: Mon, 16 Mar 2009 10:59:20 -0500

On Mar 16, 2009, at 10:57 AM, Karl Heinz Marbaise wrote:

> Hi,
>
> i've found the following entry which indicated an merge to 1.6
> branch....
> Does this mean to have developer visible change entry ?
>
> ------------------------------------------------------------------------
> r35993 | hwright | 2009-02-19 17:05:23 +0100 (Thu, 19 Feb 2009) | 7
> lines
> Changed paths:
> M /branches/1.6.x
> M /branches/1.6.x/STATUS
> M /branches/1.6.x/subversion/libsvn_fs_fs/tree.c
>
> Merge r35950 from trunk:
>
> * r35950
> Make fsfs implementation of svn_fs_commit_txn adhere to API
> promises.
> Votes:
> +1: pburba, rhuijben, gstein
>
> based on the associated log entry:
>
> ------------------------------------------------------------------------
> r35950 | pburba | 2009-02-18 03:38:45 +0100 (Wed, 18 Feb 2009) | 5
> lines
>
> Make fsfs implementation of svn_fs_commit_txn adhere to API promises.
>
> * subversion/libsvn_fs_fs/tree.c
> (svn_fs_fs__commit_txn): If the commit fails then the *NEW_REV
> argument
> should be SVN_INVALID_REVNUM.
>
> I would say yes ?

I would agree.

-Hyrum

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1334079
Received on 2009-03-16 16:59:38 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.