Wine and OpenSearch

[GOUJON Alexandre]

Hi,

When your app doesn't work on wine, you need to open a wine source file 
and try to understand what does it do and what goes wrong.
Even if they're named explicitly, you may have to look at its code.
And so you're asking where can this function be defined ?
You can use the command line with find but I prefer using "grep" feature 
available at http://source.winehq.org/git/wine.git/?a=shortlog because 
you can then open in your web browser the file exactly where you want.

And you may read something like "solved by commit xxx" on bugzilla 
without a link.
In this case, I also open the same URL as above and click on any 
commitdiff link.
I cut the end of the new URL and paste what I read previously.

So, I wondered : "Hey ! Why don't you use your search plugins to do that !"
(I'm on Firefox but all web browsers have this feature too)

Here is why I wrote these two xml.
Two lines have to be included on the server side.
And the good news is it's even compatible with IE.

Should I send these at wine-patches ?
Any comment ?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wine_commitdiff.xml
Type: text/xml
Size: 478 bytes
Desc: not available
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20100327/8f094135/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wine_git.xml
Type: text/xml
Size: 503 bytes
Desc: not available
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20100327/8f094135/attachment-0001.bin>