BUT... svn:ignore'd files never go to the repository. Each user must
svn:ignore their own files. In your scenario, User A might
svn:temporary the files in his fancy_module/subdir, but if that never
makes it up to the repository, how is it going to help User B? In order
for that attribute to go to the repository and propagate to User B, the
file must go to the repository, too. If the file is going to the
repository anyway, then that already takes care of the problem.
-----Original Message-----
From: Folker Schamel [mailto:schamel23@spinor.com]
Sent: Thursday, December 18, 2003 10:59 AM
To: Steve Dwire
Cc: John Peacock; users@subversion.tigris.org
Subject: Re: Proposal: svn:temporary property
[snip]
> Now, the part I don't understand from Folker is how the svn:temporary
> attribute fixes anything. Either the temporary files are in the
> repository, or they aren't. If they were in the repository, things
would
> work already, won't they? If they were never in the repository, how do
> you propose to attach an attribute to them?
Today, when having such files, you use svn:ignore
to tell subversion to ignore these files.
You set this property to the directory(!) containing these files.
The proposal is that instead of setting svn:ignore as today,
you use svn:temporary in the same way.
svn:ignore and svn:temporary work in the same way,
except that if the directory is deleted,
files selected by svn:temporary can be deleted silently
by the subversion client instead of generating an error.
Cheers,
Folker
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Dec 18 18:20:30 2003