Greg Stein <gstein@lyra.org> writes:
> > Revert needs to reset the state flags for the thing it is reverting
> > (removing any scheduling and conflict markers, etc.). For directories,
> > the state is kept in two places.
> >
> > Let's say we are reverting A/D/G -- as 'svn revert A/D/G', not '(cd
> > A/D/G; svn revert)'. State for A/D/G is assumed to be stored in two
> > places:
> >
> > (1) In A/D/G's entries file, as schedule= and conflicted= on the
> > "svn:this_dir" entry.
> >
> > (2) In A/D's entries file, as the same items on the entry for the "G".
>
> Why is the schedule/conflicted stuff kept in both places? Seems like a
> potential for skew/incorrectness.
This allows someone to perform versioning operations on directories
without the directory actually being there. For example, if the code
would so allow, I could do
svn rm -f A/D/G
G would now be missing from disk (and therefore, so would its entries
file), but A/D would still have a notation that G is scheduled for
removal from revision control.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:00 2006