Re: Pinning a working copy to a revision

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.

If you really want to break the connection to the repository, export a
copy instead of checking it out. A cleaner approach is to copy to a
branch where you can fix the bug and afterwards merge your changes back
to the trunk.

-- 
   Les Mikesell
     lesmikesell_at_gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org