Subversion is not a resident program that works in the background on your
computer, it only runs when you ask it to.
The only way Subversion would be able to warn you about opening up a
readonly file was if it was resident and had some sort of way to tell wether
your 3rd party software is able to detect and warn about this readonly flag
on its own or not.
If your painting tool isn't capable of detecting this and warning you about
it, there is nothing Subversion in its present state can do about it.
Perhaps a 3rd party subversion client would be able to but I suspect this
kind of feature would fall quite far down on the list of things to look
into.
For instance, what if you want to copy the file to somewhere else, or just
view the file? How would Subversion know that this way of opening the file
is "safe" and does not have to be warned about, compared to a painting
program that doesn't detect readonly states?
I think your key sentence is the opening sentence of your last paragraph:
"I really need the painting tool to warn me"...
Yes, you really need your *painting tool* to warn you.
On Tue, Mar 4, 2008 at 2:58 PM, <Nick.Thompson_at_infineon.com> wrote:
> -----Original Message-----
> From: Bicking, David (HHoldings, IT)
> >
> > -----Original Message-----
> > From: Reedick, Andrew
> > > In this case, 'svn:needs-lock' is there from the beginning (which is
>
> > > why the readonly flag is set,) and that this is more of a
> > > reminder/warning that one of your Applications changed your readonly
>
> > > file without your knowledge. More importantly, 'svn:needs-lock' is
> > > already being cached by the workspace, so all the lock information
> is
> > > already present.
> ...
> > > A gui client could implement this on their own as a
> > > courtesy feature
> > > without worrying about breaking standards (kind of like how Version
> > > Trees are not standard.) For the command line folks, it
> > > would be more
> > > convenient (and thus more like to be used) if 'svn status'
> > > would flag
> > > any modified, no local lock, 'svn:needs-lock' file.
> >
> > That makes a whole lot of sense. Perhaps something can be
> > implemented then!
>
> I don't understand how this helps. If I've just spent all day air
> brushing somebody out of a photo, how will being told by Tortoise, say,
> that I've wasted my time a few seconds or minutes after I save it help
> me? If nobody else has the lock or had the lock, I might get away with
> it, but if another users has got/had the lock and spent all day adding a
> UFO in to the background or adding horns and a tail to the person I've
> just air brushed out, this feature gains me little. I will find out as
> soon as I try to commit anyway.
>
> I really need the painting tool to warn me the file is read only/not
> locked by me before I start. Or maybe wrap the tools in a checking
> script that warns the user before starting the tool. This way I should
> be reminded to get the lock and not waste my time editing.
>
> Nick.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: users-help_at_subversion.tigris.org
>
>
--
Lasse Vågsæther Karlsen
mailto:lasse_at_vkarlsen.no
http://presentationmode.blogspot.com/
PGP KeyID: 0xBCDEA2E3
Received on 2008-03-04 15:21:24 CET