On Wed, Feb 10, 2010 at 12:33, fredck <fredck_at_gmail.com> wrote:
> I understand your point here Andy, but you're simply taking the easy
> way for TSVN. It impact on the svn command line, but TSVN is impacted
> in the same way, so it's TSVN interest to have it working..
>
> I'm not even saying that it's a bug on TSVN. I'm saying that, Win7 x64
> is becoming a popular OS, and *TSVN* users may not be able to use it.
> I have quite a standard Win7 installation, and it didn't work since
> the beginning. Also, as you can see in the this thread, I'm not the
> only one here.
>
> So, instead of taking the "it's not my fault, so I don't care"
> position, I'm suggesting being "ok, let's try to understand what's
> going on here".
It's not "the easy way out" - it's the correct approach. If the
problem is in the core Subversion libraries, then this needs to be
reported to THOSE DEVELOPERS so that they can fix it. If the TSVN
developers were to develop a workaround that only benefits TSVN users,
when what of users who use the command line client? Or any other
client, for that matter? Plus, the code bases start diverging - TSVN
should work WITH the SVN libraries, not AROUND them.
If a TSVN developer can find the root of the problem and submit a
patch back to the core SVN libraries, fine - but there's more manpower
available if it's reported to the core developers too.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2446477
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-02-10 19:02:39 CET