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

Re: Feature request: ignore-on-commit setting in repository

From: Felix Saphir <felix.saphir_at_kantarmedia.de>
Date: Mon, 01 Nov 2010 17:09:27 +0100

Am 01.11.2010 16:40, schrieb Jaap Taal:
> What I forgot to point out: With all of the suggested workarounds,
> all checkouts need to be configured before they work, so a user
> action is needed, if there are lot's of files (like env configs, but
> also mock database files (e.g. sqlite)) you need a readme.txt...
> We want to avoid this without scripting everyting. Also we want to
> apply this "auto ignore-on-commit" to existing project, so tailoring
> our software towards svn (which is a bad idea) is something we can't
> do...
> Right now we have a list of templates to copy, but when somebody
> updates the template nobody get's noticed automatically, whilst
> having the ignore on commit can actually merge incoming (new
> settings) with your changed config.
> So ignore-on-commit is ideal, but not automatic (you need to know
> which files to add to ignore on commit).

How would ignore-on-commit magically notify users of an update? How
would ignore-on-commit magically merge changes in the template to a copy
of that file? If you put the customised files under version control,
then this is what you have to deal with.


P.S. Please quote some context


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-11-01 17:09:49 CET

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

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