removed redundancy

This commit is contained in:
Dan Olson 2000-04-18 19:34:58 +00:00
parent bee04ebe8f
commit 9005810ac5
2 changed files with 0 additions and 34 deletions

View file

@ -1,20 +1,3 @@
<P>The State of the Code address is a not-frequenetly-enough updated
article written by <a href="mailto:knghtbrd@debian.org">Knghtbrd</a>
primarily for QuakeForge developers and other people who consider
themselves to be knee deep in the code, whether they happen to be
writing it or just testing it. What you won't find here is a lot of
the fluff news that tells the casual onlooker that the project is
actually doing stuff without really telling you what the state of
things are.
<P>No attempt will be made to soften technical issues so anyone can
understand them. If you want to really know what's going on, you
probably don't want details left out because they might not make a
whole lot of sense to a non-coder. Feedback is always welcome. So
are corrections if they're necessary - contrary popular (with him)
belief, Knghtbrd has in fact been known to be wrong sometimes. He
isn't afraid to admit it either (most of the time..)
<H2>How are things going? Your SotC update is late again.</H2> <H2>How are things going? Your SotC update is late again.</H2>
<P>Yeah yeah, I know. Okay, first the quick news: Palisade is <P>Yeah yeah, I know. Okay, first the quick news: Palisade is
back. The website is still under construction but it got a lot back. The website is still under construction but it got a lot

View file

@ -1,20 +1,3 @@
<P>The State of the Code address is a not-frequenetly-enough updated
article written by <a href="mailto:knghtbrd@debian.org">Knghtbrd</a>
primarily for QuakeForge developers and other people who consider
themselves to be knee deep in the code, whether they happen to be
writing it or just testing it. What you won't find here is a lot of
the fluff news that tells the casual onlooker that the project is
actually doing stuff without really telling you what the state of
things are.
<P>No attempt will be made to soften technical issues so anyone can
understand them. If you want to really know what's going on, you
probably don't want details left out because they might not make a
whole lot of sense to a non-coder. Feedback is always welcome. So
are corrections if they're necessary - contrary popular (with him)
belief, Knghtbrd has in fact been known to be wrong sometimes. He
isn't afraid to admit it either (most of the time..)
<H2>The fastest SotC update ever!</H2> <H2>The fastest SotC update ever!</H2>
<P>This update is so close to the last one posted a mere six hours <P>This update is so close to the last one posted a mere six hours
ago that most of you reading it never even saw the last one. Don't ago that most of you reading it never even saw the last one. Don't