Hi everyone,
I've often encountered the following situation with SVN. A few
developers work simultaneously on some source code. Then there is often
a bunch of files which each developer changes according to his/her
individual taste and preferences, or temporary needs. These might
include program configurations or a makefile. They are often part of the
source code, and it makes sense to keep a version of these files in the
SVN repository. However, each individual developer would like to keep
his/her version of these files.
A simple example: developer A uses Intel compiler and developer B uses
GNU. They both checkout a makefile from the repository and change the
compiler name in the makefile. They then want to commit their code
modifications, but both wish to keep their own versions of the makefile.
Obviously, one could remember to revert such local modifications before
committing, but that would require a workaround unless you are willing
to lose your local changes over and over again. Besides, this procedure
is prone to human error.
This is such a common issue, that I figured I'd ask you about it first,
and perhaps submit a feature request. Something like an svn:use-local
property would do the trick. One could set the property on a file in
order to modify it and keep the local version without committing it to
the repository. One would then delete the property if any changes to
that file finally need to be committed.
What do you think? Thanks for any feedback!
Anya
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-05-04 20:20:13 CEST