public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Dmitry V. Levin" <ldv@altlinux.org>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: GLIBC Devel <libc-alpha@sourceware.org>
Subject: Re: [patch] Fix path length overflow in realpath (BZ#22786)
Date: Wed, 09 May 2018 11:11:00 -0000	[thread overview]
Message-ID: <20180509111107.GA28728@altlinux.org> (raw)
In-Reply-To: <CALoOobOyeu6SM7DGPRqmHE6Y7BckFGmEFGeeFKDKjskL4EJDuA@mail.gmail.com>

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

On Mon, Apr 09, 2018 at 11:01:50PM +0000, Paul Pluzhnikov wrote:
> Greetings,
> 
> Attached is a trivial fix, and a test case.

Paul, could you format commit messages in a git friendly way
(the first line is a terse summary, the second line is empty,
the third line starts a descriptive text) like others do, please?


-- 
ldv

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  parent reply	other threads:[~2018-05-09 11:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-09 23:02 Paul Pluzhnikov
2018-04-10  0:25 ` Paul Pluzhnikov
2018-04-10  8:08   ` Andreas Schwab
2018-04-10 14:54     ` Paul Pluzhnikov
2018-04-10 15:15       ` Andreas Schwab
2018-04-10 15:23         ` Paul Pluzhnikov
2018-04-10 15:31       ` Alexander Monakov
2018-04-10 15:44         ` Paul Pluzhnikov
2018-04-10 16:38           ` Alexander Monakov
2018-04-10 16:47           ` Andreas Schwab
2018-04-11 13:32             ` Carlos O'Donell
2018-04-17 21:01 ` Joseph Myers
2018-04-17 23:51   ` Paul Pluzhnikov
2018-04-30 21:42     ` Paul Pluzhnikov
2018-05-08 14:34       ` Paul Pluzhnikov
2018-05-08 14:59     ` Andreas Schwab
2018-05-08 15:11       ` Paul Pluzhnikov
2018-05-08 15:29         ` Andreas Schwab
2018-05-08 15:46           ` Paul Pluzhnikov
2018-05-09 11:11 ` Dmitry V. Levin [this message]
2018-05-09 14:23   ` Paul Pluzhnikov

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=20180509111107.GA28728@altlinux.org \
    --to=ldv@altlinux.org \
    --cc=libc-alpha@sourceware.org \
    --cc=ppluzhnikov@google.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).