From: Karel Zak <kzak@redhat.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH 5/7] write: Use PATH_MAX instead of MAXPATHLEN, as elsewhere.
Date: Tue, 29 May 2012 10:14:01 +0200 [thread overview]
Message-ID: <20120529081401.GL3757@x2.net.home> (raw)
In-Reply-To: <1337969778-3154-5-git-send-email-thomas@codesourcery.com>
On Fri, May 25, 2012 at 08:16:16PM +0200, Thomas Schwinge wrote:
> term-utils/write.c | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
Applied, thanks.
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2012-05-29 8:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 18:13 Portability patches for GNU/Hurd Thomas Schwinge
2012-05-25 18:13 ` [PATCH] test_pager: Repair build for non-Linux Thomas Schwinge
2012-05-29 8:00 ` Karel Zak
2012-05-25 18:16 ` [PATCH 1/7] kill, raw, rename: Don't explicitly enable for --enable-most-builds Thomas Schwinge
2012-05-25 18:16 ` [PATCH 2/7] arch, eject, elvtune: Gracefully disable on non-Linux platforms Thomas Schwinge
2012-05-29 8:01 ` Karel Zak
2012-05-25 18:16 ` [PATCH 3/7] last, login, write: Provide a fallback for MAXHOSTNAMELEN, as elsewhere Thomas Schwinge
2012-05-29 8:10 ` Karel Zak
2012-05-29 8:40 ` Thomas Schwinge
2012-05-25 18:16 ` [PATCH 4/7] login: Include <linux/major.h> only if it exists Thomas Schwinge
2012-05-25 18:16 ` [PATCH 5/7] write: Use PATH_MAX instead of MAXPATHLEN, as elsewhere Thomas Schwinge
2012-05-29 8:14 ` Karel Zak [this message]
2012-05-25 18:16 ` [PATCH 6/7] write: Don't explicitly include <asm/param.h> Thomas Schwinge
2012-05-29 8:14 ` Karel Zak
2012-05-25 18:16 ` [PATCH 7/7] setsid: Include <sys/ioctl.h> instead of <termio.h> Thomas Schwinge
2012-05-29 8:14 ` Karel Zak
2012-05-29 8:01 ` [PATCH 1/7] kill, raw, rename: Don't explicitly enable for --enable-most-builds Karel Zak
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=20120529081401.GL3757@x2.net.home \
--to=kzak@redhat.com \
--cc=thomas@codesourcery.com \
--cc=util-linux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.