From: Robert Love <rml@tech9.net>
To: Shane Shrybman <shrybman@sympatico.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [FIXED] 2.5 evolution problem
Date: 12 Jan 2003 13:47:28 -0500 [thread overview]
Message-ID: <1042397247.834.50.camel@phantasy> (raw)
In-Reply-To: <1042395383.2397.8.camel@mars.goatskin.org>
On Sun, 2003-01-12 at 13:16, Shane Shrybman wrote:
> The bug causing problems with the evolution address book is fixed in
> 2.5.56. I don't know if it was fixed in 2.5.55 or 2.5.56 but it was
> broken in 2.5.54.
It was fixed in 2.5.55.
It works for me now, too, without using a hacked ORBit.
> This bug(#112) is listed as RESOLVED at bugme.osdl.org. Should it be
> moved to CLOSED?
I guess so.
> Also how would one find out what the resolution was at bugme.osdl.org?
> Is there a pointer to patch or cset that I missed somewhere there?
Not sure if you can.
You can find the fix posted to lkml, though - Michael Meeks posted it.
It was a simple fix in the getpeername() code as we thought.
Robert Love
next prev parent reply other threads:[~2003-01-12 18:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-12 18:16 [FIXED] 2.5 evolution problem Shane Shrybman
2003-01-12 18:47 ` Robert Love [this message]
2003-01-12 19:26 ` Shane Shrybman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1042397247.834.50.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shrybman@sympatico.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox