From: Scott Bronson <bronson@rinspin.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: smp_num_cpus undeclared workaround
Date: 14 Aug 2002 20:35:03 -0700 [thread overview]
Message-ID: <1029382505.20412.96.camel@emma> (raw)
In-Reply-To: <Pine.LNX.4.44L.0208142155190.23404-100000@imladris.surriel.com>
On Wed, 2002-08-14 at 17:55, Rik van Riel wrote:
> Looks like Evolution is Darwinian, after all ;)
Unfortunately for me, yes. PEBKAC: I needed to use "Save as Draft," not
"Send Later."
And, now, this 100% reproducible link error is not reproducing for me.
I thought I had it. Bah! Well, I'll continue to keep an eye out for
it.
- Scott
prev parent reply other threads:[~2002-08-15 3:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-15 0:15 smp_num_cpus undeclared workaround Scott Bronson
2002-08-15 0:25 ` Scott Bronson
2002-08-15 0:55 ` Rik van Riel
2002-08-15 3:35 ` Scott Bronson [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=1029382505.20412.96.camel@emma \
--to=bronson@rinspin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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.