public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/45808] FreeBSD: -pthread is handled incompletely
Date: Tue, 28 Sep 2010 14:00:00 -0000	[thread overview]
Message-ID: <20100928140000.Aq5uhqfPhl5tbPpQQ9sNmKt71lPz-HEn20JsfCYMp9Q@z> (raw)
In-Reply-To: <bug-45808-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45808

Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |manu at gcc dot gnu.org

--- Comment #4 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2010-09-28 08:28:07 UTC ---
(In reply to comment #3)
> 
> (In reply to comment #2)
> > Patches should be posted to gcc-patches@gcc.gnu.org
> 
> And, in fact, I did that a (short?) while ago:
> http://thread.gmane.org/gmane.comp.gcc.patches/217482/focus=217484
> But it seems that nobody has picked it so far.
> Perhaps I am the one to blame for that given the incorrect attachments.

http://gcc.gnu.org/contribute.html

If you do not receive a response to a patch that you have submitted within two
weeks or so, it may be a good idea to chase it by sending a follow-up email to
the same list(s). Patches can occasionally fall through the cracks. Please be
sure to include a brief summary of the patch and the URL of the entry in the
mailing list archive of the original submission.

If you do not have write access and a patch of yours has been approved, but not
committed, please advise the approver of that fact. You may want to point out
lack of write access in your initial submission, too.

And point 6 here:

http://gcc.gnu.org/wiki/GCC_Research


  parent reply	other threads:[~2010-09-28  8:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-27 12:23 [Bug target/45808] New: " avg at icyb dot net.ua
2010-09-27 16:19 ` [Bug other/45808] " rguenth at gcc dot gnu.org
2010-09-28 13:39 ` avg at icyb dot net.ua
2010-09-28 14:00 ` manu at gcc dot gnu.org [this message]
2010-09-29 11:09 ` gerald at pfeifer dot com
2011-02-14  0:46 ` [Bug target/45808] " gerald at gcc dot gnu.org
2011-02-25 23:19 ` gerald at gcc dot gnu.org
2014-08-20 23:24 ` manu at gcc dot gnu.org
2014-08-21  6:35 ` gerald at pfeifer dot com

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=20100928140000.Aq5uhqfPhl5tbPpQQ9sNmKt71lPz-HEn20JsfCYMp9Q@z \
    --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).