RE: Re: Need to check a file out, but want never to check it back in !
From: Richard M Willis <RichardW_at_pulsar-pm.com>
Date: Fri, 5 Nov 2010 02:23:54 -0700 (PDT)
> > [EditorOptions] [ProjectFiles]
The act of comitting the changes does not harm anything, no. It does, however, clutter up what's going on from one change to the next and, more importantly, the presence of a red exclamation mark on an unchanged (to me) file, means I can no longer quickly see whether "anything has changed" or not. I no more want to see a red exclamation mark on that file than I would on, say, a .map file (because the date (and only the date) changes every time). It's like the other chap says about compiler warnings. I don't want to be warned about something and then have to do an additional check to see whether it has really changed or not.
As I hinted, this particular file was the minimal form of my problem; there are other files which behave in a (more) stupid way and have more complex rules determining whether they have "changed". I asked about this particular simple file, hoping to use the results to make it handle these more complex files sensibly.
The consensus is that it can be done, but in a way that is far too unclean to get the people here to accept it.
The problem (for me) is that (T)SVN delivers a "version controled tree" and that is all; I want it to deliver a "project" with non-trivial relations between (a small number of) the files. (T)SVN handles the notion of a "project" very badly and this, for me, is what has been turning me away from SVN this past year.
If I can't do anything server-side, I will have to move to another CMS, otherwise management won't go for it: too much reconfiguration of individual machines
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
This is an archived mail posted to the TortoiseSVN Users mailing list.