Bazaar as Subversion replacement

[Nicholas Allen]

>> Unless it is as easy as Subversion's implementation there is no way we
>> could migrate without this. It is the number one show stopper for us.
>>     
>
> Well, I'm afraid you'll be waiting a long time.
>   
Is this not high on the priority list? Is it really so hard to 
implement? I can't imagine this is only a show stopper for us. There 
must be a lot of people who do cross platform development and this would 
also prevent them from using bzr...
> One of the uses of this is to find out who last changed the file.
>   
>
> Pardon me, but why does that matter?
>   
You find a class that no longer behaves the way you expect it. So you 
want to see who recently changed that class and review the recent commit 
messages to see the most what the most likely culprit is. Is that such 
an uncommon situation? I guess if you know where(ie what line) the bug 
was introduced then you could use annotate and this is often the case 
but sometimes we just want to see what the recent changes were to a 
class that may have caused it to misbehave... It's just one way of 
working but I guess you could also use annotate and check the likely 
points in the code that could cause the problem and see who changed them.
>   
>>>> 5 Olive: No easy way to see differences in a graphical diff program such
>>>> as Beyond Compare.
>>>>     
>>>>         
>>> I expect it's a few hours' work, given an interested developer.
>>>
>>> It's easy enough with the difftools plugin, though.
>>>       
>> Do you mean that this can already be done?
>>     
>
> It can be done on the commandline, not in Olive.
Ok. It should be easy enough to add to olive and we would even put a 
developer on this. I don't think it will be a major issue but it's 
something we would need in order to keep the same workflow that we are 
currently used to.