Hi Bill,

That's ok, I've found the related messages ( thanks again Pavel ) ... :D

I'm actually trying to run the BUILD RELEASE Step, but there are many =20=

files that fail to compile I have to manualy patch all of them ...

Thanks.

Le 20 sept. 06 =E0 18:56, Bill Studenmund a =E9crit :

> On Wed, Sep 20, 2006 at 03:56:33PM +0200, KlinT wrote:
>> Hi,
>>
>> Thanks for such a quick answer ...
>>
>> Le 20 sept. 06 ? 15:26, Thomas E. Spanjaard a ?crit :
>>
>>> I think that's unrelated. Read the log message. Uebayashi's patch
>>> does fix things, though: see
>>> 20060920.191421.104033642.uebayasi@brains.co.jp.
>>
>> This is an EMail adress ... Not a link :(
>
> Actually, it's not an EMail address. You're right it's not a link.
>
> It's a message ID.
>
> If you look at the headers in the message you sent, you'll find:
>
> In-Reply-To: <45114183.5040304@netphreax.net>
> References: <36E616D4-48C9-43F7-83B8-4F6688FE5468@klintcentral.net>
> <4D0AE48D-CCE7-4150-A1C8-4A9D5AC96C20@klintcentral.net>
> <274190120609200619h2db98df8o3aa76e35e30992f0@mail.gmail.com>
> <45114183.5040304@netphreax.net>
> Content-Type: text/plain; charset=3DISO-8859-1; delsp=3Dyes; =
format=3Dflowed
> Message-Id: <3A9C169F-500D-48E1-98DD-42614DD18D13@klintcentral.net>
>
> The Message-Id: line gives an ID to your message.
>
> Your mail system generates different message IDs than uebayasi's sytem
> did, so they look a little different. Yours uses lots of hex, =20
> brains.co.jp
> uses decimal. But it all serves the same purpose.
>
> The advantage of using a message ID from an EMail for identifying the
> EMail is that it is a unique property of the message. Regardless of =20=

> the
> system that archives the EMail, the message ID stays the same. So =20
> you can
> always find the right message.
>
> Take care,
>
> Bill