RFC: TortoiseBzr strategies

[Alexander Haro]

Hi,

I'm the student who worked on TortoiseBzr for last year's GSoC
program.  I wanted to let you know that your analysis of the existing
code is pretty much spot on.  However, I wanted to explain the reason
behind the decision to recursively walk the directories.  At the time
TBZR was written, recursing the tree was the only way to see if a
child inside the directory had been modified.  Hopefully this is no
longer the case, but if it is, then perhaps you should add that as
something that should be completed as part of the project.  Also,
please excuse most of the code, as I was new to Python at the time.
Feel free to contact me if you have any questions about the existing
TortoiseBzr code.

I'm really excited to see this project move forward!

Cheers
Alex

On Thu, Mar 27, 2008 at 4:34 PM, Mark Hammond <mhammond at skippinet.com.au> wrote:
> Hi all,
>   I've attached a document which outlines a couple of strategies we can take
>  for moving forward with TortoiseBzr (the Windows Shell integration).  I
>  think the document is fairly self-explanatory, although it stops short of
>  making concrete recommendations - the intent of the document is to inform
>  the decision makers!  It attempts to provide enough background material so
>  people unfamiliar with Windows Shell extensions can still understand the
>  issues.
>
>  I invite all interested parties to make comment on this document.  I will
>  act on all feedback I get, after which I intend submitting it as a merge
>  request for doc/developers - but obviously feedback on that process is
>  welcome too.
>
>  Thanks,
>
>  Mark
>