Re: [ANNOUNCE] Gerrit Code Review 2.0.3

[Jacob Helwig <jacob.helwig@gmail.com>]

On Tue, Feb 17, 2009 at 08:44, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Tue, 17 Feb 2009, Jacob Helwig wrote:
>
>> On Tue, Feb 17, 2009 at 07:18, Shawn O. Pearce <spearce@spearce.org> wrote:
>> > Gerrit is known to not work in Internet Explorer.  As an open source
>> > developer, my primary desktop system runs Linux.  My portable laptops
>> > all run Mac OS X, because its shiny.  I have no system capable of
>> > running Internet Explorer, nor do I desire to send dollars towards
>> > Redmond in order to obtain an OS license in order to do so.
>> >
>> > Something is busted in the IE AJAX code used by Gerrit Code Review.
>> > I'm guessing that instead of making the data available to the AJAX
>> > callback, IE wants to save it as a file on disk.  No clue why.
>> > And due to the lack of IE, I am unable to debug the problem myself.
>> > I am waiting for someone who really cares about using IE to debug
>> > it and contribute the patch back.
>> >
>>
>> I've found IEs4Linux helpful for debugging IE-only issues under Linux.
>>
>> http://www.tatanka.com.br/ies4linux/page/Main_Page
>>
>> I don't recall, off hand, if it'll provide IE 7 (and the site isn't
>> working for me right now, so I can't confirm this).  It does provide
>> IE 5.0, 5.5, and 6.0, however.
>
> If I understand Shawn (and the motto "scratch your own itch") correctly,
> Shawn was not so much interested in being pointed to a way of running IE
> himself, but more in people who absolutely want to run IE themselves to go
> and fix the issues.
>
> Ciao,
> Dscho
>
>

Oh, I understand "scratch your own itch", but there's also a
difference between unable to, and unwilling to. ;-)  I wouldn't have
questioned it, or said anything, if it was simply put as: "Known
issue, but we don't use IE, so it's not a priority for us.  Patches
welcome."

(Note: I'm not saying that Shawn should be willing to, just that he's
not "unable" to. I also don't claim to know the full nuances of any
possible licensing issues.)