[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn failing commit messages.

From: <rbb_at_rkbloom.net>
Date: 2003-01-13 06:54:16 CET

On 12 Jan 2003, Karl Fogel wrote:

> <rbb@rkbloom.net> writes:
> > Can those files be written to /tmp? Is the problem that APR can't find
> > the correct temp directory portably?
> We deliberately don't write them to /tmp, because we want them a) to
> be easy to find, and b) not likely to get caught up in the automated
> cleaning sweeps that some systems run on /tmp. The principle is "Use
> /tmp, or some other system-defined tmp area, for data generated by
> Subversion; but use the current directory for data generated by a
> human", the rationale being that data generated by a human could be
> arbitrarily costly to regenerate.

Are you really concerned about some automated cleaning sweep???? You are
talking about something that failed, that is most likely going to be fixed
within an hour so that the commit will succeed. Littering the current
directory with failed commit logs seems like a great way to annoy users.
If you put these files in the .svn/tmp directory, then they are unlikely
to ever be deleted. By putting them in /tmp, the user can get to them
when he needs to, but ignore them when they aren't needed.

> > I would consider this to be a rather big problem.
> Is it so big? Just 'svn rm' them from the repository.

Oh, I did that immediately. :-)


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jan 13 06:41:00 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.