Re: Reducing "out-of-date" errors

On 7/31/06, Mark Phippard <markp@softlanding.com> wrote:

> This might be a crazy idea that goes against all of the design principles
> in the code, but would it be possible to enhance the commit process so
> that after committing revision N, any "parent folders" to the committed
> files that are at revision N - 1 be advanced to revision N? This would
> keep the folders at the HEAD revision unless another user makes commits to
> the repository. It seems safe on paper, but I do not know what the code
> implications would be.

I believe the problem with that is that automatically updating those
parent folders could potentially result in conflicts when the user is
not in a position to deal with them. Running a commit on a
subdirectory shouldn't cause conflicts in parent directories.

-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:29:57 2006