public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/24577] diagnostic informative note labelled "error"
Date: Fri, 26 Feb 2010 17:04:00 -0000 [thread overview]
Message-ID: <20100226170342.14612.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24577-6594@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from manu at gcc dot gnu dot org 2010-02-26 17:03 -------
(In reply to comment #4)
> My employer does not permit employees to contribute to open source projects due
> to IP concerns. What's your second choice?
You could lobby your employer to change their policy. I am sure there are other
free software users in your company.
Or you can get paid support from Red Hat, Codesourcery or other GCC support
service, and ask them to fix the bugs for you.
Or you can wait until a friendly volunteer comes around and fixes it gratis for
you.
--
manu at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24577
next prev parent reply other threads:[~2010-02-26 17:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 22:39 [Bug c++/24577] New: " igodard at pacbell dot net
2005-10-28 23:44 ` [Bug c/24577] " pinskia at gcc dot gnu dot org
2005-10-28 23:44 ` pinskia at gcc dot gnu dot org
2007-01-26 15:35 ` manu at gcc dot gnu dot org
2007-01-31 23:38 ` manu at gcc dot gnu dot org
2007-02-01 1:03 ` igodard at pacbell dot net
2010-02-26 16:57 ` manu at gcc dot gnu dot org
2010-02-26 17:03 ` manu at gcc dot gnu dot org
2010-02-26 17:04 ` manu at gcc dot gnu dot org [this message]
2010-02-26 17:04 ` manu at gcc dot gnu dot org
2010-02-27 17:49 ` manu at gcc dot gnu dot org
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=20100226170342.14612.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).