> >
> > Use the svn:ignore property!
>
> No, that won't do what he wants.
>
> I second that feature request, I could have needed that just
> yesterday: I've
> put a file under SubVersion control but after a few days I
> noticed that this
> file is better not versioned, so I wanted SubVersion to stop
> versioning that
> file without removing the physical file.
>
> Had to copy the file, do "svn rm" and copy it back into place.
>
I want to add my vote for such a feature. But I really want something more.
I have a configuration file that is part of my project. It contains
passwords and such for each developer. Each developer must have this file,
but each is unique for that developer. I want it to be included in the
repository, so that new developers get a copy when they first checkout the
project, but I don't want each developer's private version to be commited.
Right now I have to ignore that file and handle it outside of SVN, but that
doesn't seem right.
I want some kind of 'inactive' storage so things can be stored in the repo
but not actively tracked.
--Will
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Feb 20 14:37:37 2005