[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: Lieven Govaerts <lgo_at_mobsol.be>
Date: 2006-08-01 11:16:35 CEST

Quoting Lieven Govaerts <lgo@mobsol.be>:

> D.J. Heap wrote:
> > On 7/31/06, Garrett Rooney <rooneg@electricjellyfish.net> wrote:
> >>
> >> 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.
> >>
> >
> > svndumpfilter can also generate them.
> >
> Neither svnsync nor svndumpfilter was used on this repository. Can I
> assume that it should be impossible to create empty revisions using only
> the svn client? Or are you suggesting otherwise?

I've searched the list with 'empty revision' and found this thread:

In fact, what I see here seems to be a result of issue 2220: "svn propdel
returns success on deleting a non-existent prop". I've tested it also with
deleting a file that's already deleted which also creates an empty revision.

Since the propdel issue is already reported (I don't know about the double
delete issue) this thread can be closed.



This message was sent using IMP, the Internet Messaging Program.

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