bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Cc: KO Myung-Hun <komh78@gmail.com>
Subject: Re: [PATCH 1/7] spawn: Use special invocation for <spawn.h> on OS/2 kLIBC
Date: Tue, 19 Jan 2021 19:28:39 +0100	[thread overview]
Message-ID: <3359418.pT8n0oBs3K@omega> (raw)
In-Reply-To: <20210118164013.42063-1-komh@chollian.net>

Hi KO,

Thanks, I applied patches 1, 2, 3, 5, 6, 7, slightly modified. Some of the
things that you put into the git commit message actually better belong in
the code, as a comment.

Bruno



  parent reply	other threads:[~2021-01-19 19:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-18 16:40 [PATCH 1/7] spawn: Use special invocation for <spawn.h> on OS/2 kLIBC KO Myung-Hun
2021-01-18 16:40 ` [PATCH 2/7] yield: Fix linkage to threadlib " KO Myung-Hun
2021-01-18 16:40 ` [PATCH 3/7] stddef: Fix compilation for max_align_t " KO Myung-Hun
2021-01-18 16:40 ` [PATCH 4/7] stdlib: putenv() needs a cast " KO Myung-Hun
2021-01-19 17:54   ` Bruno Haible
2021-01-22 14:35     ` KO Myung-Hun
2021-01-31  8:32     ` KO Myung-Hun
2021-01-18 16:40 ` [PATCH 5/7] zerosize-ptr: Fix compilation " KO Myung-Hun
2021-01-19 18:10   ` Bruno Haible
2021-01-22 14:26     ` KO Myung-Hun
2021-01-18 16:40 ` [PATCH 6/7] dirent: Redefine dirfd macro as a rpl function always KO Myung-Hun
2021-01-18 16:40 ` [PATCH 7/7] spawn-pipe: Fix SIGSEGV on OS/2 kLIBC KO Myung-Hun
2021-01-19 18:28 ` Bruno Haible [this message]
2021-01-22 14:37   ` [PATCH 1/7] spawn: Use special invocation for <spawn.h> " KO Myung-Hun

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=3359418.pT8n0oBs3K@omega \
    --to=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=komh78@gmail.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).