From: Frank Gevaerts <frank@gevaerts.be>
To: linux-8086@vger.kernel.org
Subject: Re: Updates
Date: Wed, 17 May 2006 10:02:18 +0200 [thread overview]
Message-ID: <20060517080218.GA17588@gevaerts.be> (raw)
In-Reply-To: <446A895C.80205@nc.rr.com>
On Tue, May 16, 2006 at 10:24:28PM -0400, Jody wrote:
>
>
> Tom McCabe wrote:
> >I have recently discovered, as of Tuesday evening,
> >that Sourceforge's anonymous CVS for ELKS is up and
> >running (Thanks, Jody!). It hasn't been edited in a
>
> I didn't do ANYTHING. Mike might have. I didn't understand why it was
> BROKEN in the first place.
Have a look at
http://sourceforge.net/docman/display_doc.php?docid=2352&group_id=1
Sourceforge has had CVS problems for more than a month, but they seem to
be solved now.
Frank
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
next prev parent reply other threads:[~2006-05-17 8:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 23:55 Updates Tom McCabe
2006-05-17 2:24 ` Updates Jody
2006-05-17 2:32 ` Updates Vikas Kumar
2006-05-17 2:42 ` Updates Jody
2006-05-17 8:02 ` Frank Gevaerts [this message]
2006-05-18 7:16 ` Updates Vojtěch Sázel
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=20060517080218.GA17588@gevaerts.be \
--to=frank@gevaerts.be \
--cc=linux-8086@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