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

Re: Bug in helpfile and status display feature request

From: Oto BREZINA <otik_at_Printflow.sk>
Date: 2006-09-30 22:39:19 CEST

Alexander Klenin wrote:
> On 9/29/06, Stefan Küng <tortoisesvn@gmail.com> wrote:
>> If the IDE requires files to work but then changes them every time you
>> simply open a project, then that IDE is flawed (sorry, but that's
>> true). I know I also have to deal with such IDE's in my office. But I
>> always write a bug report to the company responsible for the IDE, and
>> until now I always got an answer back that I'm right and that they
>> will fix it in a later release.
> Would you please write bug report to Borland then? ;-)
> The problem is not limited to IDE config files, but to other configs
> as well. It is often hard to separate config settings into "mutable by
> developer" and "common for all developers", so usually such configs
> contain some developer-specific changes which should not be committed.
> But sometimes where are changes, like addition of a new settings,
> which must be propagated (and merged with local changes).
> This schema works very well for us except the constant annoyance of
> unchecking configs.
>> > I'd really like to have some special tortoise attribute for this
>> kind of files. The status check then can flag them as modified, but
>> not propagate the modified state to the parent folder(s). And the
>> commit dialog could make
>> > these files deselected by default (while still offering them for
>> commit).
>> Bad idea. Very bad.
>> If you have a file which you (almost) never want to commit and
>> therefore always have deselected in the commit dialog, then that means
>> that TSVN has to do a non-recursive commit. And non-recursive commits
>> are limited: you can't non-recursively commit a folder deletion or a
>> folder rename/move.
> Hm. However, it will still be better then current state, when I, like
> original poster, have to (almost) always de-select these files
> manually. Besides, folder rename/deletion is very rare operation.
> How about extending pre-commit hook functionality to allow it to
> uncheck files?
> This utility seems general enough to be desirable even without the use
> case discussed now.
> > > Maybe you can consider putting this onto the issue tracker.
>> Sorry, but no.
> This is unfortunate, but such is life ;)
> Nevertheless, TortoiseSVN stays one of the best tools I use for
> development.
May be I lost something, but Isn't it Blind for this? (I have never use
it but is should do work here)

We have same problem. In Borland there is some configuration files for
project containing for forms. As I use 2 monitor on station a 1 motitor
on laptop, is hard to keep form position in not anoying state. I manualy
check if there are changes only of position or also in other settings.
Most anoying thing was about DEBUG and RELASE. We have found that best
way is: Before commit make relase build and test it and commit after that.

I plane test use hookscripts ....
Is there any good manual? for client and server version?
Is posible to use version control on this client script with project?
When I set any skript for precommit will this setting be send by commit
(so other developer will use same script)?

To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sat Sep 30 22:37:07 2006

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

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