bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Margaret Lewicka <margaret@meaningless.name>
To: Eric Blake <eblake@redhat.com>
Cc: bug-gnulib@gnu.org
Subject: Re: What happened to open_memstream.c?
Date: Fri, 13 Feb 2015 21:18:25 +0000	[thread overview]
Message-ID: <CAM3RJY_i8CSEr06RpSzcTQuSdp87Li3DF7TM=FEJYs6Cqkc2Qg@mail.gmail.com> (raw)
In-Reply-To: <54DE5A46.5060004@redhat.com>

On 13 February 2015 at 20:10, Eric Blake <eblake@redhat.com> wrote:
[...]
> I never completed the work at the time, because libvirt found another
> solution for where it would have used open_memstream.  I suppose I could
> revive the patches, if they are still useful.  Could you post the
> version of the patches that you are using, to give me a leg up on
> cleaning up my old work?

I'm using open_memstream.c as it was posted, with the exception of
removing the HAVE_FUNOPEN conditional from open_memstream.c (darwin
does have funopen(), just the define isn't set). I've also thrown the
_GL_FUNCDECL_SYS (open_memstream, FILE *, (char **, size_t *));
into stdio.in.h, without the surrounding checks.

I can mail the patch, of course, but it's really just
https://www.mail-archive.com/bug-gnulib@gnu.org/msg18077.html minus
all the files except open_memstream.c.


-- 
M.


      reply	other threads:[~2015-02-13 21:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-13 19:53 What happened to open_memstream.c? Margaret Lewicka
2015-02-13 20:10 ` Eric Blake
2015-02-13 21:18   ` Margaret Lewicka [this message]

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

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAM3RJY_i8CSEr06RpSzcTQuSdp87Li3DF7TM=FEJYs6Cqkc2Qg@mail.gmail.com' \
    --to=margaret@meaningless.name \
    --cc=bug-gnulib@gnu.org \
    --cc=eblake@redhat.com \
    /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).