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

Non-incremental ordering of commit times.

From: Erik Huelsmann <ehuels_at_gmail.com>
Date: 2005-12-05 11:29:22 CET

On 12/5/05, Peter N. Lundblad <peter@famlundblad.se> wrote:
> On Mon, 5 Dec 2005, Ph. Marek wrote:
> > On Monday 05 December 2005 10:41, Brandt, Servatius wrote:
> >
> > Is the svn:date set by the server or given by the client?
> Server. It's done by the versioned filesystem when a transaction is
> started.

There may be an issue about this somewhere, but this can cause
non-increasing commit times, if a large commit is started before a
small one and completes after it. So, non-incremental commit-times may
not only be caused by loading different dump streams into 1
repository, we cause them ourselves too.

Shouldn't we set svn:date just before finalizing the transaction?



PS: This may not be a problem with most OSS repositories, but I expect
it to be a bigger problem in corporate environments, where server load
may be heavier at specific hours.
Received on Mon Dec 5 11:30:35 2005

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.