You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Erik Huelsmann <eh...@gmail.com> on 2005/12/05 10:29:22 UTC

Non-incremental ordering of commit times.

On 12/5/05, Peter N. Lundblad <pe...@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?

bye,

Erik.

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.

Re: Non-incremental ordering of commit times.

Posted by Ben Collins-Sussman <su...@red-bean.com>.
On 12/5/05, Erik Huelsmann <eh...@gmail.com> wrote:

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

Hm, I thought we did that already... set svn:date at both the
beginning and end of the commit....

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org