Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.programming > #5177 > unrolled thread

Re: I correct some typos , please read again...

Back to article view | Back to comp.programming

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: I correct some typos , please read again... Samuel W Flint <swflint@flintfam.org> - 2015-02-02 17:15 -0600
    Re: I correct some typos , please read again... Kaz Kylheku <kaz@kylheku.com> - 2015-02-02 23:53 +0000

#5177 — Re: I correct some typos , please read again...

Instead of writing a new message, try using the "cancelling" feature of
your news reader.  Then re-post.


-- 
Samuel W. Flint
"The most dangerous phrase in the language is, 'We've always done it
this way'."  -- Grace Hopper

[toc] | [next] | [standalone]

#5178

On 2015-02-02, Samuel W Flint <swflint@flintfam.org> wrote:
> Instead of writing a new message, try using the "cancelling" feature of
> your news reader.  Then re-post.

That is the same thing as writing a new message.

Fixing a message is done with supersede.

Cancel and supersede aren't reliable. If your server allows them all (cesspools
like the one I'm using don't), there is no guarantee that these updates will
reach all the same places that the original reached. Then you end up with
sitautions like the original is still present in some servers and canceled in
others.  (Or the old version is present in some servers and the superseded one
in others.)

It's best to treat Usenet as immutable, and follow up to your own post with
corrections. Quote the minimal amount of context necessary for the errata;
don't re-post the whole thing.

And don't put your foot in your mouth in a major way, of course.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.programming

csiph-web