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

Re: Issue: empty commit(no changes) in an fsfs repository.

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2006-07-31 17:34:41 CEST

On 7/31/06, Lieven Govaerts <lgo@mobsol.be> wrote:
> Hi,
> in one of our repositories we found an empty revision. Empty meaning: author,
> date and log message are filled in correctly, but no changes were stored.
> Clients are TortoiseSVN 1.2.3 on Windows 2000, server is svn 1.2.3 with ra_dav
> on SLES 9.
> I checked the mailing list archive and issue tracker with the query 'empty
> commit' and couldn't find anything at all. I'm wondering of this is a known
> issue in svn 1.2.3? It looks like a problem with setting/changing a property on
> a folder.

I'm not sure about any known problem that could cause that, but I do
know that it's perfectly possible to have empty commits like that.
svnsync can generate them, for example, when you don't have access to
any of the changed paths in a given revision. I'd be interested to
see if you could reproduce the problem manually with the command line
client though.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 31 17:42:01 2006

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.