[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn:use-local feature request?

From: Frank Gruman <fgatwork_at_verizon.net>
Date: Sun, 04 May 2008 16:38:29 -0400

The way that we implement the feature you are asking for is to use the
svn:ignore property in each developer's working copy. This enables a
user to actually check a copy of that file back in if necessary global
changes are made, but still allow individual developers to ignore that
file when performing update / commit operations.

I will admit - I wish there was a way to set a global ignore list (from
the server) to set this property and then certain users could remove the
property if they need to make changes rather than trying to make sure
that every developer sets up the properties the right way when we get
new developers / new machines.

Hope that helps.


On Fri, 2008-05-02 at 16:54 -0700, Anna Kelbert wrote:

> 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 22:39:36 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.