From: Ian Lance Taylor <iant@google.com>
To: "René Bürgel" <rbuergel@web.de>
Cc: Christopher Jefferson <chris@bubblescope.net>, gcc-help@gcc.gnu.org
Subject: Re: [C++0x unique_ptr] sorting a vector of unique_ptr fails
Date: Tue, 16 Dec 2008 06:14:00 -0000 [thread overview]
Message-ID: <m38wqgejfw.fsf@google.com> (raw)
In-Reply-To: <4946EC3E.8040504@web.de> (=?utf-8?Q?=22Ren=C3=A9_B=C3=BCrgel?= =?utf-8?Q?=22's?= message of "Tue\, 16 Dec 2008 00\:46\:06 +0100")
René Bürgel <rbuergel@web.de> writes:
> Maybe i can take a closer look at this during the xmas holiday and
> create a patch to fix this issue. Would this need any paperworks with
> the FSF?
Yes, a patch for this would require paperwork with the FSF. If you
are interested, let me know, and I will send you what you need to
start the process. Thanks.
Ian
next prev parent reply other threads:[~2008-12-16 6:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-13 17:35 René Bürgel
2008-12-15 19:30 ` Ian Lance Taylor
2008-12-15 20:22 ` Christopher Jefferson
2008-12-15 23:46 ` René Bürgel
2008-12-16 6:14 ` Ian Lance Taylor [this message]
2008-12-17 0:44 ` René Bürgel
2008-12-17 0:50 ` Diego Novillo
2008-12-17 1:06 ` Diego Novillo
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=m38wqgejfw.fsf@google.com \
--to=iant@google.com \
--cc=chris@bubblescope.net \
--cc=gcc-help@gcc.gnu.org \
--cc=rbuergel@web.de \
/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).