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

RE: enforcing LF-normalization for svn:eol-style=native files (issue #4065)

From: Bert Huijben <bert_at_qqmail.nl>
Date: Mon, 10 Dec 2012 15:29:50 +0100

> -----Original Message-----
> From: Branko Čibej [mailto:brane_at_wandisco.com]
> Sent: maandag 10 december 2012 8:04
> To: dev_at_subversion.apache.org
> Subject: Re: enforcing LF-normalization for svn:eol-style=native files (issue
> #4065)
> On 10.12.2012 07:35, Bert Huijben wrote:
> > I don’t think you have to wait until commit time: You could verify the
> > commit base revision’s properties + changes. In the cases where the
> > properties change before commit, the commit would fail for being out of
> > date.
> That would imply you can't change properties and contents in the same
> commit, wouldn't it. Which I suspect is not the case? :)
> The problem is worse, you can theoretically reopen and modify a
> transaction any number of times before committing it, so you don't
> really know until txn commit time which properties actually apply to
> which file contents.

On the fs layer this is probably true, but in a normal editor drive through the ra layers this should never happen.

On the ra layer the final set of properties is valid in the file_close() callback. I'm just not sure if this is really an event that the server sees for ra_dav, or if this is implied by the committing.

Received on 2012-12-10 15:30:32 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.