Doug Porter <dsp@waterspout.com> writes:
> One problem with using $PWD that I don't think has been pointed
> out yet is that $PWD might be a directory in which the user does
> not have write access. If that is the cause the commit will
> fail, and that is lame.
If $PWD fails, then using a tmp dir is certainly better than failing,
yah.
> Users of both Unix and Windows systems expect temporary files to
> be created in the proper place. I haven't seen any compelling
> benefit to not doing it right.
Does that include this portion from my previous mail:
> Obviously, the vacation example is a fantasy, but in real life
> interruptions do happen, and you may have to walk away from your
> computer for an arbitrary amount of time. We should never be storing
> the *only* copy of user-generated data in /tmp.
>
> When other programs use /tmp, they're usually storing derived data
> there. If the operation is interrupted, and the file left in /tmp is
> either never found or is cleaned out by a broom-bot, it's not a big
> deal.
>
> But this case is different. This file is our only record of the
> user's log message. In a complex commit, it could represent a few
> hours of work. /tmp is the wrong place for important data like that.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 13 18:29:39 2002