On 8/1/06, Mark Phippard <markp@softlanding.com> wrote:
> I do not know, that is why I asked. I think it would help, and it goes a
> little beyond this trivial use case. You could have done an
> update/checkout so that you were at HEAD, then done a commit, now you want
> to do a rename or property set. If it so happened that there had not been
> other activity on your project, then that last commit would have kept your
> folders up to date and you could perform the operation without an update.
See, the problem here is that it's making the problem rarer, but not
making it go away entirely, so all you're doing is delaying the user
running into it, which means when they do hit it they're less likely
to know what's wrong.
> Another possibility, but I suspect it would be an even bigger change would
> be to be less agressive about bumping folder revisions. As I understand
> it, if I modify a file and commit it, the parent folder (or is it all
> parent folders) has its revision bumped. I think that some other tools
> that manage folders would only do it when files are added/deleted or the
> folder properties are changed.
I'm not clear what you mean by being less agressive about bumping
folder revisions. The bubble up bumping of parent folders in the
filesystem is a core feature of the filesystem, it's how it works, and
making it go away would be, uhh, hard. Did you mean something else?
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 1 16:57:48 2006