This is the mail archive of the
mailing list for the GCC project.
Re: CppCoreGuidelines warnings
- From: Jason Merrill <jason at redhat dot com>
- To: Manuel LÃpez-IbÃÃez <lopezibanez at gmail dot com>
- Cc: Christopher Di Bella <cjdb dot ns at gmail dot com>, Jonathan Wakely <jwakely dot gcc at gmail dot com>, gcc Mailing List <gcc at gcc dot gnu dot org>
- Date: Tue, 17 May 2016 13:58:14 -0400
- Subject: Re: CppCoreGuidelines warnings
- Authentication-results: sourceware.org; auth=none
- References: <CACL3gUVfYsaM5ddp5+sfQ3Q+E2VKzRHjnntO-xs1Zwpvu2ca4A at mail dot gmail dot com> <CAH6eHdSXrMBZRHqu2qfAG-rbhxk+GiXmYhvDVP=fnq2HL3HB_Q at mail dot gmail dot com> <573279E9 dot 6020709 at gmail dot com> <CACL3gUUS8goAThsL6gyDJV7wdU8KmFTX2Bx0aBqNCpB8VjFAaw at mail dot gmail dot com> <CAESRpQDN5dqi+jtq-9RK=T-Tz0AJfbWKWdTzefo40A8CWzZq_w at mail dot gmail dot com>
On Tue, May 17, 2016 at 8:51 AM, Manuel LÃpez-IbÃÃez
> Please also note that, in terms of legal papers, the FSF is much more
> flexible than one may think, but they are not very pro-active or fast
> (in my past experience, things may have changed now). If you find some
> internal resistance at your company, it would be good to figure out
> what are the key issues for your employer and what are the possible
> trade-offs, then explain them to the FSF legal team. If there is any
> possible solution at all, they will surely find it out. But it would
> be better to discuss all possibilities with your employer to avoid
> wasteful back and forth.
It might work better to put your employer in touch with the FSF so you
don't have to mediate in a game of telephone; I believe firstname.lastname@example.org
is the right address to use.