From: Pavel@Janik.cz (Pavel Janík)
Subject: Re: Assignment procedure these days?
Date: Tue, 31 Dec 2002 11:41:55 +0100 [thread overview]
Message-ID: <m37kdqjwr0.fsf@Janik.cz> (raw)
In-Reply-To: <843cofs0as.fsf@lucy.cs.uni-dortmund.de> (kai.grossjohann@uni-duisburg.de's message of "Mon, 30 Dec 2002 21:45:47 +0100")
From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Date: Mon, 30 Dec 2002 21:45:47 +0100
> > To save 1 hop the hacker can print, sign and send the paper first; than
> > they will sign it and snail it back. At least, it work for me this way
> > earlier this year.
>
> That's also how it worked for me, but now the procedure appears to
> have been changed, for whatever reason.
The reason is simple: people are sending this paper when we need them to
send another paper. The first hop is for getting the *right* paper.
--
Pavel Janík
The more I learn about Linux kernel issues, the more I am considering to start
looking for Something Else(tm)... ;-)
-- Lars Marowsky-Bree in private e-mail
prev parent reply other threads:[~2002-12-31 10:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-30 15:48 Lars Magne Ingebrigtsen
2002-12-30 17:44 ` Kai Großjohann
2002-12-30 18:07 ` Lars Magne Ingebrigtsen
2002-12-30 19:24 ` Karl Eichwalder
2002-12-30 20:45 ` Kai Großjohann
2002-12-31 10:41 ` Pavel Janík [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=m37kdqjwr0.fsf@Janik.cz \
--to=pavel@janik.cz \
/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).