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

Re: SV: Re: Re: Re: Extending TortoiseSVN/Subversion

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2006-08-11 19:52:50 CEST

Jared Hardy wrote:
> On 8/9/06, Stefan Küng <tortoisesvn@gmail.com> wrote:
>> "limit status scans to affected paths" - ok, try to understand here:
>> fetching the status of a single path is very expensive (see 'bug' report
>> above). Imagine you did an update/commit of 100 files, your working copy
>> consists of 10000 files in 100 folders. Fetching the status for those
>> 100 files would be the same as fetching the status for the whole working
>> copy. (assuming all 100 folders have the same amount of files in them).
>
> I understand what you're saying, but you don't seem to understand the
> importance of my emphsis on *non recursive* status checks. You seem to
> have ignored this line entirely: "It shouldn't take much logic to
> detect when multiple files are in the same directory, and just run the
> status [fetch] on that directory once non-recursively".

No, I haven't ignored that line. But I'm always a little surprised when
people who haven't sent in one simple patch for this project can assume
the amount of work it needs for a certain feature they want. I wonder
why it's always "not much", no matter what they're asking for.

>> I don't know how you're working in your project. But it really seems you
>> should better change your project a little.
>
> That's right, you don't know my project. So stop trying to dictate
> policy via seemingly arbitrary interface choices. Yes, I said
> "arbitrary". Given the non-recursive status fetch optimization
> mentioned above, I don't see how "update" and "status refresh" are any
> different from the existing options "revert" and "lock".

You really think that you can get me motivated to work on this with that
attitude of yours?
That said, I suggest to drop this issue completely for at least a week
until you calmed down a little. Then we might be able to discuss this
further.

To help you calm down: Subversion 1.5 will have some new APIs to support
changesets. With those, keeping the commit dialog open can be done a
little easier and will be implemented.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Aug 11 19:53:00 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.