From: Matthias Andree <matthias.andree@gmx.de>
To: Jochen Friedrich <jochen@scram.de>,
Matthias Andree <matthias.andree@gmx.de>,
Andreas Dilger <adilger@turbolabs.com>,
sam@ravnborg.org
Cc: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Documentation/BK-usage/bksend problems?
Date: Sun, 5 Jan 2003 13:00:29 +0100 [thread overview]
Message-ID: <20030105120029.GC5686@merlin.emma.line.org> (raw)
In-Reply-To: <20030105075842.GA1256@mars.ravnborg.org>
Sam Ravnborg schrieb am Sonntag, den 05. Januar 2003:
> I will submit this with bk sendbug now.
Thank you. It looks as though the bkbugs stuff expected the list of
interested parties in a different syntax; when I added my findings, it
complained about the real names in that list, such as "user Jochen not
found" or something like that. Looks like it's not RFC-822 "To:" header
syntax but just a set of mail addresses.
--
Matthias Andree
next prev parent reply other threads:[~2003-01-05 11:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-05 1:54 Matthias Andree
2003-01-05 7:42 ` Jochen Friedrich
2003-01-05 7:58 ` Sam Ravnborg
2003-01-05 12:00 ` Matthias Andree [this message]
2003-01-05 14:55 ` Larry McVoy
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=20030105120029.GC5686@merlin.emma.line.org \
--to=matthias.andree@gmx.de \
--cc=adilger@turbolabs.com \
--cc=jochen@scram.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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
Powered by JetHome