From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org, Agustina Arzille <avarzille@riseup.net>
Subject: Re: [hurd,commited] hurd: Reimplement libc locks using mach's gsync
Date: Tue, 20 Mar 2018 01:59:00 -0000 [thread overview]
Message-ID: <20180320015948.zcuxpzjnx5drgraa@var.youpi.perso.aquilenet.fr> (raw)
In-Reply-To: <alpine.DEB.2.20.1803191644190.4537@digraph.polyomino.org.uk>
Joseph Myers, on lun. 19 mars 2018 16:57:07 +0000, wrote:
> But actually nothing else defines GSYNC_SHARED
Actually gnumach does. This is used to avoid having to depend on a
recent version of its headers.
Samuel
prev parent reply other threads:[~2018-03-20 1:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-18 17:24 Samuel Thibault
2018-03-19 16:57 ` Joseph Myers
2018-03-19 21:31 ` Joseph Myers
2018-03-20 1:59 ` Samuel Thibault [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180320015948.zcuxpzjnx5drgraa@var.youpi.perso.aquilenet.fr \
--to=samuel.thibault@ens-lyon.org \
--cc=avarzille@riseup.net \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.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).