Re: Ignore certain file

[Quinn Taylor]

This is not a limitation of Versions per se, but of using versions control (such as Subversion) in general. If a file is versioned and changes are made, the SCM software will naturally present the file as eligible for committing. The common solution for the situation you mention is to only version a generic template version of the config file (e.g. "config.php.tmpl") and set the containing directory to ignore "config.php". Each developer can then create and maintain their own config.php without fear of screwing up anyone else's config.

 - Quinn

On Oct 1, 2009, at 7:57 PM, chaoszcat wrote:

If you remove a file from the repository and commit, then when other developers update, Subversion will want to remove the file on everyone else's working copy, which is likely not what you want.

I have been looking for solution for this feature to be implemented in
Versions.
When you have files like config.php, and the file contains settings
specific to different developers, why can't we have the option to
ignore the file while committing? It seems to be quite handy anyway.

The method of ignoring file seems to be only to remove it, follow by
committing, meaning, removing the server copy. I wonder, if I remove
this copy, will other developers still get the file? No right?

Any other solution?

--~--~---------~--~----~------------~-------~--~----~

To post to this group, send email to versions@googlegroups.com
To unsubscribe from this group, send email to 
versions+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/versions?hl=en
-~----------~----~----~----~------~----~------~--~---

You received this message because you are subscribed to the Google Groups "Versions" group.

smime.p7s
Description: S/MIME cryptographic signature