public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de>
To: Roland McGrath <roland@redhat.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
	GNU libc hackers <libc-hacker@sources.redhat.com>
Subject: Re: bits/in.h patch
Date: Fri, 20 Apr 2007 16:01:00 -0000	[thread overview]
Message-ID: <m31wifyqzd.fsf@gromit.moeb> (raw)
In-Reply-To: <20070402202006.C4965180064@magilla.sf.frob.com> (Roland McGrath's message of "Mon\, 2 Apr 2007 13\:20\:06 -0700 \(PDT\)")

[-- Attachment #1: Type: text/plain, Size: 714 bytes --]

Roland McGrath <roland@redhat.com> writes:

>> Roland McGrath <roland@redhat.com> writes:
>> 
>> > The Hurd does not have working ipv6 support yet, and when it does it will
>> > be fine to have it use the Linux numbers for socket options in the user API
>> > (it will probably be using the Linux ipv6 code anyway).  
>> 
>> So, should my patch go in?  Or how should we solve this?
>
> I think it's fine.

Ok, submitted now, - and closed the PR,

Andreas
-- 
 Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/
  SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
   Maxfeldstr. 5, 90409 Nürnberg, Germany
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

      reply	other threads:[~2007-04-20 16:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-18 13:48 Andreas Jaeger
2007-02-19  5:56 ` Ulrich Drepper
2007-02-19  8:15   ` Andreas Jaeger
2007-02-19  9:05     ` Ulrich Drepper
2007-02-19  9:55   ` Roland McGrath
2007-03-24 16:28     ` Andreas Jaeger
2007-04-02 20:32       ` Roland McGrath
2007-04-20 16:01         ` Andreas Jaeger [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=m31wifyqzd.fsf@gromit.moeb \
    --to=aj@suse.de \
    --cc=drepper@redhat.com \
    --cc=libc-hacker@sources.redhat.com \
    --cc=roland@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).