From: Dan Christensen <jdc@chow.mat.jhu.edu>
Cc: bugs@gnus.org, ding@gnus.org
Subject: Re: error when reparenting
Date: Tue, 12 May 1998 18:01:35 -0400 [thread overview]
Message-ID: <x7g1ifrvwg.fsf@chow.mat.jhu.edu> (raw)
In-Reply-To: Kim-Minh Kaplan's message of "11 May 1998 01:39:47 +0200"
Kim-Minh Kaplan <KimMinh.Kaplan@utopia.eunet.fr> writes:
>
> I have been looking more deeply into the problems with loops in the
> References: header which I first noticed due to Hrovje's report. I
> now think I have a more bullet proof solution that should also correct
> Dan Christensen's problem.
I just applied the patch and it fixes the problems I was having.
(Messages being omitted from the summary buffer due to bad references
headers.) I'll let you know if any problems arise.
Thanks Kim-Minh!
Dan
--
Dan Christensen
jdc@math.jhu.edu
prev parent reply other threads:[~1998-05-12 22:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <x7yaywyj8l.fsf@chow.mat.jhu.edu>
[not found] ` <m3d8g76h5w.fsf@sparky.gnus.org>
[not found] ` <x7vhtqjok3.fsf@chow.mat.jhu.edu>
[not found] ` <m3ra2k7qvu.fsf@sparky.gnus.org>
[not found] ` <x7wwcbt0u2.fsf@chow.mat.jhu.edu>
1998-05-10 23:39 ` Kim-Minh Kaplan
1998-05-12 22:01 ` Dan Christensen [this message]
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=x7g1ifrvwg.fsf@chow.mat.jhu.edu \
--to=jdc@chow.mat.jhu.edu \
--cc=bugs@gnus.org \
--cc=ding@gnus.org \
/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;
as well as URLs for NNTP newsgroup(s).