mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Solar Designer <solar@openwall.com>
To: musl@lists.openwall.com
Subject: Re: Daily reports: Friday
Date: Wed, 13 Jul 2011 23:46:02 +0400	[thread overview]
Message-ID: <20110713194602.GA26189@openwall.com> (raw)
In-Reply-To: <4E187422.6070601@gmail.com>

Luka -

On Sat, Jul 09, 2011 at 05:30:42PM +0200, Luka Mar??eti?? wrote:
> Oh, ok. I should've ommitted the "-cont" I agree. However, being Re:'s 
> to each other, I hope they still fall under the same thread.

JFYI:

"Re:" has nothing to do with threading, which normally works based on
Message-Id/In-Reply-To/References headers (this is what blists uses, and
I think Gmane does as well).  So you may completely change the Subject,
but as long as you use your MUA's "reply" feature, you add to the same
thread.  Some mailing list archives do substring match on Subjects,
though - I think MARC does.  But adding "Re:" doesn't help them either.

> As an 
> orientation, I may use the latest commits eg "strn.c + comon/String.c" 
> as part of the Subject, or I may drop differentiation completely and 
> just have us rely on time stamps. In the end, there's always this to 
> monitor specific commits: https://github.com/lmarcetic/cluts/commits/master

Please continue to post daily reports.  Start the message Subjects with
"cluts: " and follow that with either the report's date (e.g., "07/13")
or specific info on changes made (e.g., "such-and-such tests").

And please continue to post weekly reports as well - on Mondays.  These
should summarize your accomplishments for last week and describe what
you intend to work on next.  I feel that the daily communication, while
very helpful, is no replacement for weekly summaries.

Thanks,

Alexander


  parent reply	other threads:[~2011-07-13 19:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-05  0:41 Daily reports: Monday Luka Marčetić
2011-07-05 14:24 ` Daily reports: Tuesday Luka Marčetić
2011-07-06 20:28   ` Daily reports: Wednesday Luka Marčetić
2011-07-07 16:18     ` Szabolcs Nagy
2011-07-07 20:27       ` Luka Marčetić
2011-07-07 20:16     ` Daily reports: Thursday Luka Marčetić
2011-07-08 22:41       ` Daily reports: Friday Luka Marčetić
2011-07-09  1:12         ` Daily reports: Friday - cont Luka Marčetić
2011-07-09  1:38           ` Solar Designer
2011-07-09 11:53         ` Daily reports: Friday Solar Designer
2011-07-09 15:30           ` Luka Marčetić
2011-07-09 22:11             ` Luka Marčetić
2011-07-13 19:46             ` Solar Designer [this message]
2011-07-10 14:52           ` Daily reports: Friday (threaded setuid testing) Rich Felker
2011-07-11 22:59             ` Daily cluts reports Luka Marčetić
2011-07-14  9:57               ` cluts: strerror_r() test (was: Daily cluts reports) Solar Designer
2011-07-14 10:41                 ` cluts: strerror_r() test Luka Marčetić
2011-07-14 10:47                   ` Solar Designer
2011-07-14 17:55                   ` Rich Felker
2011-07-14 19:35                     ` Luka Marčetić
2011-07-15  0:09               ` Daily cluts reports Luka Marčetić
2011-07-15 22:47                 ` Daily cluts reports - numeric, setuid, and mid-term evaluation Luka Marčetić
2011-07-15 23:51                   ` Rich Felker
2011-07-17  0:37                   ` Daily cluts reports - setuid reiteration Luka Marčetić

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=20110713194602.GA26189@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).