public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Shea Levy <shea@shealevy.com>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>, linux-kernel@vger.kernel.org
Subject: Re: When to re-post or give up on a message
Date: Sat, 1 Oct 2011 21:27:06 +0200	[thread overview]
Message-ID: <20111001192706.GF18690@1wt.eu> (raw)
In-Reply-To: <20111001205040.3b56bceb@stein>

On Sat, Oct 01, 2011 at 08:50:40PM +0200, Stefan Richter wrote:
> On Oct 01 Shea Levy wrote:
> > If a new thread is posted to the list without any response, how long 
> > should the poster wait before losing any expectation of a response? 
> > Under what circumstances should the poster then re-post, and when should 
> > he just give up on that thread? Sorry to have to ask this on the list, 
> > but I can't find it on the faq anywhere.
> 
> It depends on what it is about --- e.g. an urgent patch vs. an obscure bug.
> 
> But much more important than /when/ to repost is /how/ to repost.  If you
> did not get a response, then maybe
>   - the subject,
>   - the Cc list (subsystem mailinglists, people), or
>   - the description of your issue
> was lacking.  If you possibly can, find out more about the issue and where
> to send to before you repost.
> 
> It is better to repost (though not too frequently) than to give up.  But
> it is *much better* to repost with better researched and explained
> information (and, if applicable, with better Cc list) than to repost the
> same message.

And just for the record, here are a few additional hints (which don't
particularly apply to Shea's message, I found it and it was correct) :

  - don't write the subject in uppercase, that's used by spammers only
  - use a correct "From" field, not one looking like a spam or a young geek
    who wants to impress friends. This means you have first and last names.
  - put the most important information at the beginning of the subject, because
    a number of us check the list in a terminal lying in a corner. On my 80x25
    xterm, here's how your mail appears :

    10666     Sep 29 shea@shealevy.c (  25) Hang with "runaway loop modprobe net-pf-

    With the version-relevant parts on the left, it tends to attract the
    reader's eye more efficiently, especially for people who have made
    changes in this version :

    10666     Sep 29 shea@shealevy.c (  25) 3.0.4 regression: runaway loop modprobe net-pf-1

  - ensure your mail describes a problem and asks for clear questions. Do not
    just send an information expecting someone to comment on it.

Sometimes it's wise to wait 3-4 days if this is not urgent because someone
will feel concerned by your subject. If the problem is urgent for you,
indicate it in the message, but not in the subject as those are often
considered offensive. You will notice that many people read a lot of
mails without replying because they have nothing to say. If you're
clearly asking for some help, some readers may forward your message
to relevant people.

It's common to let bug reporters search a bit when they appear capable
of digging by themselves, because it's the only way to scale. That's
why it's important to clearly say when you've reached your limits and
are seeking for help. For instance, concerning your report, some readers
will wonder whether it's a 3.0-3.0.4 regression or a more general
2.6.39-3.0 regression, and they will naturally wait for you to report
this precision. Since you appear capable of trying different kernels,
this is something you should check yourself and report by responding
to your message.

Regards,
Willy


  reply	other threads:[~2011-10-01 19:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-01 17:54 When to re-post or give up on a message Shea Levy
2011-10-01 18:50 ` Stefan Richter
2011-10-01 19:27   ` Willy Tarreau [this message]
2011-10-01 18:59 ` Mark Knecht

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=20111001192706.GF18690@1wt.eu \
    --to=w@1wt.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shea@shealevy.com \
    --cc=stefanr@s5r6.in-berlin.de \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox