On 7/27/07, Julien Nigay <killergege@gmail.com> wrote:
> Hi !
>
> I think a new feature would be great in Tortoise : the ability to "hide" a
> file that exists in the repository and that is under version control.
>
> - Why ?
> Because sometimes you need to modify a file and you don't want to commit the
> change. The problem is that this file will appear each time you'll want to
> commit the project's files and you are sure that one time you will forget to
> uncheck it and it will be commited. It's not the end of the world if it
> happens but it could result in time loss.
>
> - Example ?
> I use Eclipse. In order to have the same configuration on all computers, its
> config files are versioned. The problem is that I may not have the exactly
> the same environment (different file paths) and I may want a special
> configuration option only on my computer and not published in the
> repository.
>
> - How ?
> I don't want that the file doesn't appear in the commit dialog box because
> the risk is that the developper forgets that file.
> So, an "ignored" (find a better term) file should appear in the dialog box
> but with its checkbox unchecked and displayed in a special color so that the
> user can see he has an ignored file.
>
>
> So that feature would enable the user to indicate that he doesn't want that
> file to be commited until he has decided to.
> Unless you can give me another way to do that, it would be a useful feature
> for me (I have other cases where I'd like to have this feature).
> I tried to ignore the file in the properties but it seems that it's not
> working, the versioned files are not ignored (or I don't use it correctly).
>
> I'm not sure it should be a Tortoise or Subversion feature...
The standard advice is: http://subversion.tigris.org/faq.html#ignore-commit
What I have done with my applications is to split the configuration
files up. "Global" settings go in one config file named
global.properties. Settings which are specific to a particular OS go
in a config file named OPERATINGSYSTEM.properties (where
OPERATINGSYSTEM is Linux, Windows XP, Windows 2003, etc.). Settings
which are specific to a particular computer go in a config file named
COMPUTERNAME.properties. At build- or run-time (depending on what
you're doing), the build system or the application itself determines
which config files it needs to load.
By doing this, the primary developer, who works on Linux, our servers
(some of which run Win2K, some Win2K3) and I (running WinXP) all have
our configurations set appropriately, without having to screw around
with changing configurations which would mess another environment up.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Fri Jul 27 14:49:14 2007