[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: D.J. Heap <djheap_at_gmail.com>
Date: 2006-08-01 02:23:29 CEST

On 7/31/06, Garrett Rooney <rooneg@electricjellyfish.net> wrote:
> 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.
> -garrett

svndumpfilter can also generate them.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 1 02:23:56 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.