From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Score help...
Date: Mon, 29 Apr 2002 13:31:35 +0200 [thread overview]
Message-ID: <vafn0vmvizs.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <87adrmajso.fsf@nwalsh.com> (Norman Walsh's message of "Mon, 29 Apr 2002 06:19:51 -0400")
Norman Walsh <ndw@nwalsh.com> writes:
> Well, this is what M-i a L ... etc. created. But if the format is wrong,
> that'd explain why it doesn't work :-)
Hm. The "extra" looks fishy. But what do I know -- I don't grok
scoring.
kai
--
Silence is foo!
next prev parent reply other threads:[~2002-04-29 11:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-28 20:13 Norman Walsh
2002-04-29 9:43 ` Kai Großjohann
2002-04-29 10:19 ` Norman Walsh
2002-04-29 11:31 ` Kai Großjohann [this message]
2002-04-29 11:50 ` .overview parsing bug? [was Re: Score help...] Norman Walsh
2002-04-29 14:28 ` Karl Kleinpaste
2002-04-29 14:34 ` Norman Walsh
2002-04-29 12:08 ` Score help Karl Kleinpaste
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=vafn0vmvizs.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--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).