mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Solar Designer <solar@openwall.com>
To: musl@lists.openwall.com
Subject: keep discussion threads separate (was: Simple testing task - string functions)
Date: Sun, 10 Apr 2011 19:46:21 +0400	[thread overview]
Message-ID: <20110410154621.GA7871@openwall.com> (raw)
In-Reply-To: <4DA1CC07.5000102@gmail.com>

JIghtuse -

On Sun, Apr 10, 2011 at 10:25:59PM +0700, JIghtuse wrote:
> I have some questions about my task. I've written a program to test 
> malloc() function of musl. But..

That's great, but why are you posting to the thread about "string
functions" (a task for Luka)?  Please be careful to post to the proper
thread.  I suggest that you re-post your message to the proper thread
now (by replying to Rich's message with your task definition), quoting
some relevant context, and any replies should be posted to that other
message (in the proper thread).  Otherwise, we'll mix the two threads up
badly.

Please note that threading typically works based on Message-ID,
In-Reply-To, and References headers, not on Subjects (although this is
sometimes done as well).  So simply setting the Subject to match that of
the right thread won't be enough.  Please actually locate Rich's message
that you want to reply to, and use the reply feature of your MUA on it.
That message was:

Date: Fri, 8 Apr 2011 19:34:02 -0400
To: musl@lists.openwall.com
From: Rich Felker <dalias@aerifal.cx>
Subject: Re: [musl] GSoC

You may optionally change the Subject to "malloc testing (was: GSoC)"
(notice how the previous Subject is preserved after "was:").

To learn on what context to quote and how, please refer to:

http://www.complang.tuwien.ac.at/anton/mail-news-errors.html
http://www.netmeister.org/news/learn2quote.html

Thanks,

Alexander


  parent reply	other threads:[~2011-04-10 15:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-10  4:45 Simple testing task - string functions Rich Felker
2011-04-10 12:08 ` Luka Marčetić
2011-04-10 15:25 ` JIghtuse
2011-04-10 15:34   ` Rich Felker
2011-04-10 15:46   ` Solar Designer [this message]
2011-04-14 17:59 ` Luka Marčetić
2011-04-14 23:11   ` Rich Felker
2011-04-18 12:20     ` Luka Marčetić
2011-04-25 19:34     ` Unit tests Luka Marčetić
2011-04-26 19:14       ` Solar Designer
2011-04-27  0:32         ` Rich Felker
2011-04-27  0:42       ` Rich Felker
2011-04-27  6:29         ` Luka Marčetić
2011-04-29  5:36           ` Solar Designer
2011-04-29 11:54             ` Christian Neukirchen
2011-05-01 19:36               ` Solar Designer
2011-05-02  8:51                 ` Christian Neukirchen
2011-05-02 12:49                   ` Solar Designer
2011-05-02 13:02                     ` errno
2011-05-02 13:11                       ` Rich Felker
2011-05-02 13:30                         ` Solar Designer
2011-05-02 13:32                           ` Rich Felker
2011-05-02 13:52                             ` Solar Designer
2011-05-02 13:27                       ` Solar Designer

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=20110410154621.GA7871@openwall.com \
    --to=solar@openwall.com \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).