public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/53339] unordered_map::iterator requires Value to be complete type
Date: Wed, 16 May 2012 02:14:00 -0000	[thread overview]
Message-ID: <bug-53339-4-F0rxQoWehZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53339-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #18 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-05-16 02:12:31 UTC ---
(In reply to comment #16)
> I was hoping to avoid copyright assignment by having someone else
> do the work :) 

That's OK, but in that case I think (and this is just IMHO) it's better if you
don't post a series of patches.

Ideally we'd like you to sign a copyright assignment and contribute, but if you
won't or can't contribute your code then IMHO you shouldn't offer it in the
form of patches, because if we can't accept it then even reviewing your patch
might make it tricky for us to implement the suggestion in a similar way (did
we use your code? copy your idea? do we need to get a lawyer to decide if a
change we make is based on your non-assigned work? ... I don't want to have to
even ask those questions, let alone answer them!)


  parent reply	other threads:[~2012-05-16  2:12 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-13 22:23 [Bug libstdc++/53339] New: " eltoder at gmail dot com
2012-05-13 22:27 ` [Bug libstdc++/53339] " eltoder at gmail dot com
2012-05-14  2:12 ` redi at gcc dot gnu.org
2012-05-14  2:40 ` paolo.carlini at oracle dot com
2012-05-14  3:20 ` eltoder at gmail dot com
2012-05-14  5:06 ` eltoder at gmail dot com
2012-05-14  5:29 ` eltoder at gmail dot com
2012-05-14 10:54 ` paolo.carlini at oracle dot com
2012-05-14 11:15 ` paolo.carlini at oracle dot com
2012-05-14 13:14 ` paolo.carlini at oracle dot com
2012-05-14 13:29 ` paolo.carlini at oracle dot com
2012-05-15  1:11 ` paolo.carlini at oracle dot com
2012-05-15  2:09 ` eltoder at gmail dot com
2012-05-15  4:25 ` eltoder at gmail dot com
2012-05-15  9:29 ` paolo.carlini at oracle dot com
2012-05-15 10:07 ` paolo at gcc dot gnu.org
2012-05-15 10:11 ` paolo.carlini at oracle dot com
2012-05-15 12:40 ` eltoder at gmail dot com
2012-05-15 13:16 ` paolo.carlini at oracle dot com
2012-05-16  2:14 ` redi at gcc dot gnu.org [this message]
2012-05-16  2:52 ` eltoder at gmail dot com
2012-05-16  3:04 ` redi at gcc dot gnu.org
2012-05-16  9:34 ` paolo.carlini at oracle 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=bug-53339-4-F0rxQoWehZ@http.gcc.gnu.org/bugzilla/ \
    --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).