public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Roland McGrath <roland@hack.frob.com>,
	 "GNU C. Library" <libc-alpha@sourceware.org>
Subject: Re: [PATCH roland/sigvec] Remove sigvec.
Date: Sat, 04 Oct 2014 00:57:00 -0000	[thread overview]
Message-ID: <542F45CC.6070705@cs.ucla.edu> (raw)
In-Reply-To: <20141003224414.3445F2C3A61@topped-with-meat.com>

Roland McGrath wrote:
> Does anybody see any reason to be more properly conservative about removing
> sigvec?

I don't.  For what it's worth, the last mention of sigvec I can see in the Emacs 
source code is dated 1986.  Something about a Gould implementation, in assembly 
language.

  reply	other threads:[~2014-10-04  0:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-03 22:44 Roland McGrath
2014-10-04  0:57 ` Paul Eggert [this message]
2014-10-06  9:44 ` Florian Weimer
2014-10-09 19:33   ` Roland McGrath
2014-10-13  8:59     ` Florian Weimer
2014-10-13 20:24       ` Roland McGrath
2014-11-14 12:34         ` Florian Weimer
2014-11-14 19:07           ` Roland McGrath
2014-11-17  7:53             ` Stefan Liebler

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=542F45CC.6070705@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=libc-alpha@sourceware.org \
    --cc=roland@hack.frob.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).