Re: [RFC] Don't allow a non-existent path to be a tree conflict victim?

On Tue, Nov 04, 2008 at 05:36:23PM +0000, Julian Foad wrote:
> b) Ensure there is always a WC entry for a path whenever we have any
> state to record about that path. Create a WC entry, with some suitable
> state indicator that it is "unversioned" or of node kind "none", when we
> raise a conflict on such a path.

I believe this is similar to how we handle sparse files
(a feature which is not in trunk yet).

A "fake" entry is created with information saying "this file
is not present on disk, but that's OK, the user has chosen
to omit it from the working copy".

So if we did something similar for non-existent tree conflict
victims, that would be consistent.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-11-04 20:41:40 CET