From: Andy Pfiffer <andyp@osdl.org>
To: Thomas Molina <tmolina@cox.net>
Cc: Robert Love <rml@tech9.net>,
Eric Blade <eblade@m-net.arbornet.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Evolution and 2.5.x
Date: 14 Oct 2002 13:39:56 -0700 [thread overview]
Message-ID: <1034627996.1995.55.camel@andyp> (raw)
In-Reply-To: <Pine.LNX.4.44.0210141435440.6072-100000@dad.molina>
On Mon, 2002-10-14 at 12:41, Thomas Molina wrote:
> > > See this thread:
> > > http://lists.ximian.com/archives/public/evolution-hackers/2002-June/004841.html
> > >
> > > It is indeed broken in 2.5 and it is not, for once, our fault. This
> > > thread and other discussion seem to point out it is a bug in ORBit.
> > >
> > > Robert Love
> >
> > I spent some time trying to track this problem down, but reached a wall
> > due to the size and nature of the ChangeSet.
> >
> > The bitkeeper ChangeSet that made Evolution's address book hang when
> > trying to compose a new message when run on 2.5.x kernels was 1.262.2.2.
>
> I've read this thread and I'm confused. Is this seen as a problem with
> Evolution, ORBit, or the 2.5 kernel? If it is seen as a possible kernel
> problem, I'll add it to my problem report status page and track it. If I
> track it, Eric Blade will get a weekly email asking whether he's still
> seeing the problem, at least until I'm told to drop it, or no one
> responds.
I'll defer to the experts as to the root cause of the problem.
All I know for sure is that before 1.262.2.2 Evolution works, and after
applying 1.262.2.2, it doesn't.
Andy
next prev parent reply other threads:[~2002-10-14 20:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-13 18:54 Evolution and 2.5.x Eric Blade
2002-10-13 19:03 ` Robert Love
2002-10-13 19:24 ` Eric Blade
2002-10-14 18:07 ` Andy Pfiffer
2002-10-14 19:41 ` Thomas Molina
2002-10-14 19:48 ` Robert Love
2002-10-14 20:39 ` Andy Pfiffer [this message]
2002-10-15 4:48 ` Eric Blade
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=1034627996.1995.55.camel@andyp \
--to=andyp@osdl.org \
--cc=eblade@m-net.arbornet.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
--cc=tmolina@cox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.