From: Jody <jbruchon@nc.rr.com>
To: Tom McCabe <rocketjet314@yahoo.com>
Cc: linux-8086@vger.kernel.org
Subject: ELKS Patches
Date: Fri, 05 May 2006 00:41:35 -0400 [thread overview]
Message-ID: <445AD77F.5060200@nc.rr.com> (raw)
In-Reply-To: <20060505031016.54707.qmail@web51301.mail.yahoo.com>
Notice:
Because of the fact that CVS for ELKS is totally and completely broken
for anonymous usage, please send all ELKS patches to the following address:
elks@jodybruchon.com
This way, I can make the fixes to the source and periodically release
it. I do not have a CVS or SVN server to host from, and once I figure
out how in the hell the CVS got busted, the changes can be committed in
one burst. I managed to use my developer access and shell account to
checkout a copy of the ELKS CVS tree, which I will make available
shortly, but I can't seem to figure out for the life of me how the CVS
was mangled for anonymous pserver access.
If you can provide actual patch files I can apply with the patch
command, that would be most helpful.
Thanks!
Jody Bruchon
next prev parent reply other threads:[~2006-05-05 4:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 3:10 Device types Tom McCabe
2006-05-05 4:41 ` Jody [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-06 19:03 ELKS Patches Jody
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=445AD77F.5060200@nc.rr.com \
--to=jbruchon@nc.rr.com \
--cc=linux-8086@vger.kernel.org \
--cc=rocketjet314@yahoo.com \
/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.