lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111001205040.3b56bceb@stein>
Date:	Sat, 1 Oct 2011 20:50:40 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Shea Levy <shea@...alevy.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: When to re-post or give up on a message

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/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ