n Development
> > > Subject: API review - the 'commit_as_operations' flag on
> > > svn_client_commit5()
> > >
> > > I'd like to understand the new 'commit_as_operations' flag on
> > > svn_client_commit5() a bit better. First, note that the old
On Thu, 2011-06-23 at 13:33 +0200, Bert Huijben wrote:
>
> > -Original Message-
> > From: Julian Foad [mailto:julian.f...@wandisco.com]
> > Sent: donderdag 23 juni 2011 12:37
> > To: Subversion Development
> > Subject: API review - the 'commit_as_oper
> -Original Message-
> From: Julian Foad [mailto:julian.f...@wandisco.com]
> Sent: donderdag 23 juni 2011 12:37
> To: Subversion Development
> Subject: API review - the 'commit_as_operations' flag on
> svn_client_commit5()
>
> I'd like to underst
I'd like to understand the new 'commit_as_operations' flag on
svn_client_commit5() a bit better. First, note that the old commit4()
API passes FALSE. The doc string says:
* If @a commit_as_operations is set to FALSE, when a copy is committed
* all changes below the copy are always committed at
4 matches
Mail list logo
