From: Eric Weddington <eweddington@cso.atmel.com>
To: "'Robin Getz'" <rgetz@blackfin.uclinux.org>,
"'Robert Dewar'" <dewar@adacore.com>
Cc: gdb@sourceware.org, iant@google.com,
"'Anmol P. Paralkar'" <b07584@freescale.com>,
"'Jim Blandy'" <jimb@codesourcery.com>
Subject: RE: Posting from work/university addresses
Date: Sat, 04 Aug 2007 17:36:00 -0000 [thread overview]
Message-ID: <003301c7d6bd$18304c90$190412ac@corp.atmel.com> (raw)
In-Reply-To: <200708021345.43026.rgetz@blackfin.uclinux.org>
> -----Original Message-----
> From: Robin Getz [mailto:rgetz@blackfin.uclinux.org]
> Sent: Thursday, August 02, 2007 11:46 AM
> To: Robert Dewar
> Cc: gdb@sourceware.org; iant@google.com; Anmol P. Paralkar; Jim Blandy
> Subject: Re: Posting from work/university addresses
>
> On Thu 2 Aug 2007 13:10, Robert Dewar pondered:
> >
> > Let's make sure that we really know the rules before we follow them!
> > Almost no one from the EU posts this stuff, and I have never heard
> > of such a requirement in connection with our paris based company.
>
> There are some people following them now - due to company
> policy - RedHat in Cambridge
> and Analog Devices in Munich - I know for sure...
Also Atmel in Germany is definitely following this policy.
Eric Weddington
next prev parent reply other threads:[~2007-08-04 17:36 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
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 [this message]
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='003301c7d6bd$18304c90$190412ac@corp.atmel.com' \
--to=eweddington@cso.atmel.com \
--cc=b07584@freescale.com \
--cc=dewar@adacore.com \
--cc=gdb@sourceware.org \
--cc=iant@google.com \
--cc=jimb@codesourcery.com \
--cc=rgetz@blackfin.uclinux.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