public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Serge Hallyn <serge.hallyn@ubuntu.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH 2/2] linux ttyname_r: return link if appropriate
Date: Mon, 18 Apr 2016 20:03:00 -0000	[thread overview]
Message-ID: <20160418200300.GZ5369@vapier.lan> (raw)
In-Reply-To: <20160418195349.GC30476@ubuntumail>

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

On 18 Apr 2016 19:53, Serge Hallyn wrote:
> Same as previous commit for ttyname

i think it's preferable to squash it into the previous commit.
it's not like we'd merge one w/out the other.
-mike

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

      reply	other threads:[~2016-04-18 20:03 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-15 15:29 [PATCH 1/1] linux ttyname: " Serge Hallyn
2016-04-15 16:27 ` Florian Weimer
2016-04-15 16:47   ` Serge Hallyn
2016-04-15 17:06     ` Florian Weimer
2016-04-15 17:43       ` Serge Hallyn
2016-04-15 18:48         ` Serge Hallyn
2016-04-15 19:59           ` Mike Frysinger
2016-04-18 19:53             ` [PATCH 1/2] " Serge Hallyn
2016-04-18 20:02               ` Mike Frysinger
2016-04-18 20:23                 ` Serge Hallyn
2016-04-20  2:10                   ` [PATCH] linux ttyname and ttyname_r: " Serge Hallyn
2016-04-20  2:28                     ` Mike Frysinger
2016-04-20 18:51                       ` Serge Hallyn
2016-07-27 13:43                         ` Serge E. Hallyn
2016-07-27 17:28                         ` Dmitry V. Levin
2016-08-06  2:09                           ` Serge E. Hallyn
2016-08-06  8:46                             ` Mike Frysinger
2016-08-06 15:00                               ` Serge E. Hallyn
2016-08-09 20:41                                 ` Serge E. Hallyn
2016-08-09 21:18                                 ` Dmitry V. Levin
2016-08-09 21:39                                   ` Serge E. Hallyn
2016-08-09 23:26                                     ` Dmitry V. Levin
2016-08-10 23:24                                       ` Serge E. Hallyn
2016-08-10 23:48                                         ` Dmitry V. Levin
2016-08-10  6:38                                     ` Florian Weimer
2016-08-10 23:03                                       ` Serge E. Hallyn
2016-08-10 23:18                                         ` Dmitry V. Levin
2016-08-10 23:26                                           ` Serge E. Hallyn
2016-10-03  6:16                                           ` Serge E. Hallyn
2016-10-03  7:29                                             ` Andreas Schwab
2016-10-03 14:05                                               ` [PATCH 1/1] linux ttyname and ttyname_r: do not return wrong results Serge E. Hallyn
2016-10-04  9:53                                             ` [PATCH] linux ttyname and ttyname_r: return link if appropriate Florian Weimer
2016-10-04 12:47                                               ` Serge E. Hallyn
2016-04-18 19:53             ` [PATCH 1/1] linux ttyname: " Serge Hallyn
2016-04-18 19:54             ` [PATCH 2/2] linux ttyname_r: " Serge Hallyn
2016-04-18 20:03               ` Mike Frysinger [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=20160418200300.GZ5369@vapier.lan \
    --to=vapier@gentoo.org \
    --cc=libc-alpha@sourceware.org \
    --cc=serge.hallyn@ubuntu.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).