Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Robert Klemme Newsgroups: comp.lang.ruby Subject: Re: HTTP response question. Date: Tue, 22 Dec 2015 11:55:58 +0100 Lines: 25 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net t01EginMNo1iKdE36Q0NAQAvPmRcwbfE8cgBCBq2pfxu1ceeI= Cancel-Lock: sha1:THOppHSWuAa8aPqhyQ4adVAfjZA= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 In-Reply-To: Xref: csiph.com comp.lang.ruby:7171 On 21.12.2015 08:09, Michael Uplawski wrote: > But my *supersede* was posted in between my original posting and the > response that you gave. Anyway, as supersedes do not work reliably > everywhere, I could just as well abandon the practice and leave my typos > intact in the future... Intact typos vs. broken (= fixed) typos - that is hilarious! :-) > The server, that I currently use to read the news as delivered a > double message, too. OK, then technology fooled me. Thanks for clarification! > I saw your response and thank you very much, as always. You're welcome. Cheers robert -- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/