From: hpa@transmeta.com (H. Peter Anvin)
To: linux-kernel@vger.kernel.org
Subject: Re: master.kernel.org situation update
Date: 29 Jan 2002 19:16:55 -0800 [thread overview]
Message-ID: <a37oj7$q9m$1@tazenda.transmeta.com> (raw)
In-Reply-To: <a37lu4$q5a$1@tazenda.transmeta.com> <20020129191128.B23269@work.bitmover.com>
Followup to: <20020129191128.B23269@work.bitmover.com>
By author: Larry McVoy <lm@bitmover.com>
In newsgroup: linux.dev.kernel
>
> This doesn't help you now...
>
I have gotten several of this type of "helpful advice"... please lay
off. I really don't need this right now.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
prev parent reply other threads:[~2002-01-30 3:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 2:31 master.kernel.org situation update H. Peter Anvin
2002-01-30 3:11 ` Larry McVoy
2002-01-30 3:16 ` H. Peter Anvin [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='a37oj7$q9m$1@tazenda.transmeta.com' \
--to=hpa@transmeta.com \
--cc=linux-kernel@vger.kernel.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 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.