All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Charles Lepple" <clepple@ghz.cc>
To: "Samuel Flory" <sflory@rackable.com>
Cc: "Sam Ravnborg" <sam@ravnborg.org>,
	"Christoph Hellwig" <hch@infradead.org>,
	"James Simmons" <jsimmons@infradead.org>,
	"Roman Zippel" <zippel@linux-m68k.org>,
	"michaelm" <admin@www0.org>,
	linux-kernel@vger.kernel.org, vojtech@suse.cz
Subject: Re: Make menuconfig broken
Date: Tue, 22 Jul 2003 15:46:53 -0400 (EDT)	[thread overview]
Message-ID: <14435.216.12.38.216.1058903213.squirrel@www.ghz.cc> (raw)
In-Reply-To: <3F1D91F0.2020900@rackable.com>

please drop my email from the cc line-- I'll catch up on this thread later.

thanks,

-- 
Charles Lepple <clepple@ghz.cc>
http://www.ghz.cc/charles/

  reply	other threads:[~2003-07-22 19:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-21 16:35 2.6.0-test1 won't go further than "uncompressing" on a p1/32MB pc michaelm
2003-07-21 16:49 ` James Simmons
2003-07-21 17:02 ` Charles Lepple
2003-07-22  0:37   ` Samuel Flory
2003-07-22  0:42     ` Make menuconfig broken Samuel Flory
2003-07-22  7:19       ` Sam Ravnborg
2003-07-22  9:50       ` Roman Zippel
2003-07-22 13:24         ` Vojtech Pavlik
2003-07-22 16:47         ` James Simmons
2003-07-22 18:17           ` Christoph Hellwig
2003-07-22 19:16             ` Sam Ravnborg
2003-07-22 19:35               ` Samuel Flory
2003-07-22 19:46                 ` Charles Lepple [this message]
2003-07-22 20:30                 ` James Simmons
2003-07-23 22:53                   ` bill davidsen
2003-07-23 22:48             ` bill davidsen
2003-07-22 18:00         ` Samuel Flory
2003-07-22 19:21           ` michaelm
2003-07-22  2:49     ` 2.6.0-test1 won't go further than "uncompressing" on a p1/32MB pc Thomas Molina
2008-02-02 17:29 make menuconfig broken Michal Zachar
2008-02-02 19:50 ` Sam Ravnborg

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=14435.216.12.38.216.1058903213.squirrel@www.ghz.cc \
    --to=clepple@ghz.cc \
    --cc=admin@www0.org \
    --cc=hch@infradead.org \
    --cc=jsimmons@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=sflory@rackable.com \
    --cc=vojtech@suse.cz \
    --cc=zippel@linux-m68k.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.