Ulrich Eckhardt wrote:
> Hi!
>
> I'm looking for a way to pin a working copy to a certain revision in the
> repository, meaning that updating this working copy should fail. This should
> be a purely local change (otherwise I could create a tag instead).
>
> The reason I want that is that it serves me as a reminder that I updated it to
> that very revision in order to look for a certain bug. I don't want to
> accidentally update the working copy, just to get conflicts due to local
> changes or having to recompile 2M LOC just because the update changed a
> central file.
>
> Yes, I know it's my fault but I wonder if there is any however dirty hack that
> could help me.
>
>
I'd still use tag and then check that tag out separately, ie not change
the current working copy to point at that tag. If you're worried about
it messing up a nice clean tag tree then you can tag it to some private
developer area, you don't have to tag to the regular tags tree.
Simon Lucy
> Cheers!
>
> Uli
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-11-18 17:29:35 CET