[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 18:56:59 CET

On 13 Jan 2003 cmpilato@collab.net wrote:

> Kevin Pilch-Bisson <kevin@pilch-bisson.net> writes:
> > > Thoughts?
> > >
> > Not apart from the (already present) problem that someday I'd like to be able
> > to import data from a read-only medium like a cd-rom.
> I was thinking the same thing. We have talked about import
> *optionally* converting the imported dir into a working copy, but we
> should never expect to have write access to that dir.
> > Maybe we should move commit messages to ~/.subversion/ instead of
> > current directory. Then we would be able to leave the file around,
> > and still be able to have a read-only source dir.
> Or, we could (now, you might wanna sit down for this one) just MAKE

++1! Anything else is only a partial solution. If we put the commit
messages anyplace other than /tmp (or the equivalent), then EVERY svn user
has to remember to delete those files. Which, conveniently, we have just
removed from a directory that they are likely to look at. :-)

If we just use /tmp, then the user can ignore it, because the system's
regular sweep of /tmp will remove those files. (Assuming a well
maintained system).


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jan 13 18:43:57 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.