When to re-post or give up on a message

When to re-post or give up on a message

[Shea Levy]

Hi all,

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.

Cheers,
Shea Levy

Re: When to re-post or give up on a message

[Stefan Richter]

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.
-- 
Stefan Richter
-=====-==-== =-=- ----=
http://arcgraph.de/sr/

Re: When to re-post or give up on a message

[Willy Tarreau]

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

Re: When to re-post or give up on a message

[Mark Knecht]

On Sat, Oct 1, 2011 at 10:54 AM, Shea Levy <shea@shealevy.com> wrote:
> Hi all,
>
> 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.
>
> Cheers,
> Shea Levy

Hi Shea,
   I'm a long, long, long time lurker, seldom poster. I'm not a
developer but like to read about at least the big issues here.

   My experience on getting a response here has a lot to do with what
my request is. I only post here when I cannot find another place more
appropriate on my own. I'd say that out of the 20-30 threads I've
posted here over the last decade at least 95% have been responded to.
Most have gotten a response in a day or two. Some have taken a week.

   My follow-up strategy is oriented around getting someone interested
in my issue. Typically what I do is post everything I think is of
interest on the first post, and following that keep working it on my
own. If I haven't received a response in a day or two, not including
weekends, then I'll typically respond to myself with more information
gathered since the first post. Sometimes it's taken 2-3 posts to get
the eyeballs of someone who's working on the area I'm concerned with.

HTH,
Mark