From: Kurt Wall <kwall@kurtwerks.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] to Documentation/ramdisk.txt
Date: Sat, 23 Oct 2004 21:29:58 -0400 [thread overview]
Message-ID: <20041024012958.GB3245@kurtwerks.com> (raw)
In-Reply-To: <20041023200344.10839.30049.60955@localhost.localdomain>
On Sat, Oct 23, 2004 at 03:03:45PM -0500, james4765@verizon.net took 225 lines to write:
> All right - Try 3 with the sendpatchset script.
>
> Thanks to Paul Jackson for the help in getting it to work w/ my ISP.
Went right in over here...
Kurt
--
"I had to hit him -- he was starting to make sense."
prev parent reply other threads:[~2004-10-24 1:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-23 20:03 james4765
2004-10-24 1:29 ` Kurt Wall [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=20041024012958.GB3245@kurtwerks.com \
--to=kwall@kurtwerks.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®