Re: Proposal: svn:temporary property

Francois Beausoleil wrote:

> Folker, I think a recipe like the following is what you describe:

Thanks. This exactly serves my argument!

This is bad workflow in WC2, not a problem which (I believe) needs to be fixed
in Subversion (with or without a new property). wc2 is not up to date with the
repository!

>
> Here's part of the output:
> E:\>svn --version
> svn, version 0.34.0 (r7859)
> compiled Dec 4 2003, 08:08:28
> [snip]
> E:\>svn co -r1 file:///repos wc2
> A wc2\fancy_module
> A wc2\fancy_module\doit.c
> A wc2\other_module
> A wc2\other_module\doit.c
> Checked out revision 1.
>
> E:\>cd wc2

E:\> svn up
D fancy_module
Updated to revision 2.

>
> E:\wc2>echo the object module 1>fancy_module\doit.o
The system cannot find the path specified.

Had the user in wc2 updated first, the directory would have been gone, so the
new .o could not be created, thus would not have obstructed the later update. QED

A new property, which someone has to add to a directory which might, at some
point in the distant future, be deleted is not a good way to solve this problem.
  Proper user training in the use of the tools is, IMHO.

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org