From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: iant@google.com, "Anmol P. Paralkar" <b07584@freescale.com>,
gdb@sourceware.org, Jim Blandy <jimb@codesourcery.com>
Subject: Re: Posting from work/university addresses
Date: Tue, 31 Jul 2007 01:08:00 -0000 [thread overview]
Message-ID: <20070731000833.GB1092@ednor.casa.cgf.cx> (raw)
In-Reply-To: <Pine.LNX.4.64.0707301730290.10226@ld0159-tx32.am.freescale.net>
On Mon, Jul 30, 2007 at 06:07:43PM -0500, Anmol P. Paralkar wrote:
> On Mon, 30 Jul 2007, Jim Blandy wrote:
>>I've noticed a number of posters to the GDB lists recently who I'd
>>guess were professionals working on real-world stuff, but coming from
>>gmail/yahoo/hotmail accounts instead of work or university addresses.
>>From various other cues I'd guess they were from countries with growing
>>technology industries, like China, India, or Russia.
>>
>>I'm curious --- is there some reason people avoid posting to the GDB
>>mailing lists from their work/uni addresses?
>
>In the case of work address: Some companies require inclusion
>of/automatically include a disclaimer notice at the end of the message
>and sometimes it's against list policy to post messages with such
>disclaimers in them. So e.g. in the gcc list, such posters are kindly
>advised to use a free account like in:
>
>http://gcc.gnu.org/ml/gcc/2007-07/msg00732.html
>
>(Not that the advice is always heeded).
This will soon no longer be optional as I've been asked to start bouncing
messages which contain disclaimers. I'm testing the code to do this now.
cgf
next prev parent reply other threads:[~2007-07-31 0:08 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 8:14 Why does gdb implement 'next' command with a series of "vCont;s"? congli
2007-07-30 22:12 ` Posting from work/university addresses Jim Blandy
2007-07-31 0:08 ` Anmol P. Paralkar
2007-07-31 1:08 ` Christopher Faylor [this message]
2007-08-02 16:58 ` Robin Getz
2007-08-02 17:12 ` Robert Dewar
2007-08-02 17:42 ` Robin Getz
2007-08-02 18:09 ` Ian Lance Taylor
2007-08-04 17:36 ` Eric Weddington
2007-08-02 18:23 ` Jim Blandy
2007-08-02 18:34 ` Christopher Faylor
2007-08-03 12:05 ` Eli Zaretskii
2007-08-03 14:27 ` Christopher Faylor
2007-08-03 14:39 ` Ian Lance Taylor
2007-08-03 17:10 ` Eli Zaretskii
2007-08-03 23:11 ` Christopher Faylor
2007-08-04 8:41 ` Eli Zaretskii
2007-08-04 18:36 ` Ian Lance Taylor
2007-08-04 18:51 ` Eli Zaretskii
2007-08-05 0:03 ` Christopher Faylor
2007-08-05 3:51 ` Robin Getz
2007-08-05 5:07 ` Christopher Faylor
2007-08-05 12:03 ` Robert Dewar
2007-08-05 18:27 ` Christopher Faylor
2007-08-06 6:53 ` Eli Zaretskii
2007-08-06 14:04 ` Ian Lance Taylor
2007-08-06 14:22 ` Eli Zaretskii
2007-08-04 20:04 ` Bob Rossi
2007-08-05 0:06 ` Christopher Faylor
2007-08-05 1:58 ` Bob Rossi
2007-08-05 3:13 ` Eli Zaretskii
2007-08-05 4:33 ` Christopher Faylor
2007-08-06 14:07 ` Ian Lance Taylor
2007-07-31 7:59 ` Wenbo Yang
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=20070731000833.GB1092@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=b07584@freescale.com \
--cc=gdb@sourceware.org \
--cc=iant@google.com \
--cc=jimb@codesourcery.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox