From: wraeth <wraeth@wraeth.id.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] audacity-2.0.5 failed to compile
Date: Wed, 2 Sep 2015 19:50:07 +1000 [thread overview]
Message-ID: <55E6C64F.9010509@wraeth.id.au> (raw)
In-Reply-To: <55e6be5d.6307c20a.54bab.03df@mx.google.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 09/02/2015 07:15 PM, Gevisz wrote:
> On Wed, 2 Sep 2015 01:55:00 -0400 Fernando Rodriguez
> <frodriguez.developer@outlook.com> wrote:
>> It's arguable if that makes the list less productive, but
>> certainly posting a new thread every few hours about the same
>> issue will make it less productive.
>
> Agree with the last phrase: "posting a new thread every few hours
> about the same issue" should be avoided."
Okay, so identify it, communicate it, and move on.
One useful reference [1] I've come across is a description of "How to
ask questions the smart way" - a guide on what sort of information to
include and general etiquette when posting to lists and IRC etc.
Perhaps that could be referred to when suggesting improvements on how
to ask questions.
Either way, I think the point has now been covered. :)
1: http://www.catb.org/esr/faqs/smart-questions.html
- --
wraeth <wraeth@wraeth.id.au>
GnuPG Key: B2D9F759
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iF4EAREIAAYFAlXmxkgACgkQXcRKerLZ91loiwD+KvYxQjvwMVUqjW9mx5Ea1cq1
1vehX6xn9/b7xXWWsoYA/1g3FZ7wOWXrF1k9g2kcji9kfiKHNAWuPDWgN/hcc90o
=4FIl
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-09-02 9:50 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 22:04 [gentoo-user] audacity-2.0.5 failed to compile thelma
2015-09-01 22:55 ` Fernando Rodriguez
2015-09-01 23:05 ` thelma
2015-09-02 1:22 ` Alec Ten Harmsel
2015-09-02 2:23 ` Fernando Rodriguez
2015-09-02 2:57 ` wraeth
2015-09-02 4:24 ` thelma
2015-09-02 4:57 ` wraeth
2015-09-02 5:59 ` Mick
2015-09-02 11:50 ` Alan McKinnon
2015-09-02 12:04 ` Dale
2015-09-02 20:25 ` thelma
2015-09-03 13:06 ` Alec Ten Harmsel
2015-09-03 13:19 ` Alan McKinnon
2015-09-03 13:56 ` thelma
2015-09-03 14:27 ` Alan McKinnon
2015-09-03 17:22 ` Alec Ten Harmsel
2015-09-03 20:10 ` Alan McKinnon
2015-09-03 18:57 ` Fernando Rodriguez
2015-09-03 19:11 ` thelma
2015-09-03 19:30 ` Mick
2015-09-03 19:41 ` thelma
2015-09-03 20:35 ` Alan McKinnon
2015-09-04 8:34 ` Neil Bothwick
2015-09-03 19:24 ` Mick
2015-09-03 19:56 ` thelma
2015-09-03 20:41 ` Alan McKinnon
2015-09-04 8:38 ` Neil Bothwick
2015-09-04 13:24 ` Alan McKinnon
2015-09-04 21:31 ` Neil Bothwick
2015-09-04 9:42 ` Peter Humphrey
2015-09-04 10:00 ` Mick
2015-09-04 10:19 ` Peter Humphrey
2015-09-04 10:31 ` Neil Bothwick
2015-09-04 10:48 ` Peter Humphrey
2015-09-04 13:26 ` Alan McKinnon
2015-09-03 14:28 ` Neil Bothwick
2015-09-03 15:26 ` thelma
2015-09-03 15:31 ` Alan McKinnon
2015-09-03 15:33 ` thelma
2015-09-03 16:16 ` Alexander Kapshuk
2015-09-03 17:22 ` Neil Bothwick
2015-09-03 20:44 ` Dale
2015-09-02 13:28 ` [gentoo-user] " James
2015-09-02 5:55 ` [gentoo-user] " Fernando Rodriguez
2015-09-02 9:15 ` Gevisz
2015-09-02 9:50 ` wraeth [this message]
2015-09-02 18:52 ` Andreas K. Huettel
2015-09-02 20:31 ` Alan McKinnon
2015-09-03 12:47 ` Alec Ten Harmsel
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=55E6C64F.9010509@wraeth.id.au \
--to=wraeth@wraeth.id.au \
--cc=gentoo-user@lists.gentoo.org \
/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