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

Re: svn commit: rev 2541 -

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-07-16 07:19:17 CEST

cmpilato@collab.net writes:
> The dump/load thing shouldn't be affected. Why would there be a hole?
> A no-op revision still has interesting information (author, date, log)
> that would be dumped and loaded just like any other revision.

Oh, that's fine. So then our solution is: allow no-op revisions, and
make sure "svn log" handles them correctly.


> I'd rather do this than impose arbitrary restrictions on
> svn_fs_commit_txn. I still feel like we should make all our library
> layers between the client binary and libsvn_fs attempt to disallow
> no-op commits, but it certainly should *not* be ruled out at the
> libsvn_fs level. And, if one slips through the cracks, it should not
> be a burden to the rest of the functionality of Subversion (like `svn
> log').
> Though I admit I don't know the right way to fix `svn log' in this
> case.

I think it's probably not too hard; we can take a look tomorrow.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 16 07:31:01 2002

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.