linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Bug 999] New: Problem with the /dev/ptmx file
Date: Mon, 28 Jul 2003 13:04:58 -0700	[thread overview]
Message-ID: <3902340000.1059422697@[10.10.2.4]> (raw)
In-Reply-To: <20030728205501.A26278@infradead.org>

> He needs to compile in and use devpts.  But if he insists in the
> crappy bugzilla interface instead of lkml I won't tell him.

<shrug> Whatever. 

Soon it'll all be integrated anyway, so you can just send email back
to the lkml email, and it'll just cc bugzilla. 

M.


  reply	other threads:[~2003-07-28 20:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-28 19:39 [Bug 999] New: Problem with the /dev/ptmx file Martin J. Bligh
2003-07-28 19:55 ` Christoph Hellwig
2003-07-28 20:04   ` Martin J. Bligh [this message]
2003-07-28 20:09   ` Sean Estabrooks
2003-07-28 20:50     ` Nick Moffitt
2003-07-28 20:52     ` Dave Barry
2003-07-29  9:49     ` Christoph Hellwig
2003-07-28 19:40 Martin J. Bligh

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='3902340000.1059422697@[10.10.2.4]' \
    --to=mbligh@aracnet.com \
    --cc=hch@infradead.org \
    --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 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).