From: Jesper Dahl Nyerup <nyerup@one.com>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH] script: Also flush writes to timing file.
Date: Sun, 23 Feb 2014 20:20:00 +0100 [thread overview]
Message-ID: <20140223191959.GA3103@one.com> (raw)
In-Reply-To: <20140221124420.GE30903@x2.net.home>
[-- Attachment #1: Type: text/plain, Size: 417 bytes --]
On Feb 21 13:44, Karel Zak wrote:
> On Tue, Feb 18, 2014 at 08:48:45PM +0100, Jesper Dahl Nyerup wrote:
> > term-utils/script.c | 5 ++++-
> > 1 file changed, 4 insertions(+), 1 deletion(-)
>
> Applied, thanks.
>
> I have also made the files usage more robust and close all in done()
> (based on Sami's suggestion).
Thanks!
J.
--
Jesper Dahl Nyerup
Systems Engineer
One.com, nyerup@one.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2014-02-23 19:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 21:43 [PATCH] script: Also flush writes to timing file Jesper Dahl Nyerup
2014-02-18 10:08 ` Sami Kerola
2014-02-18 10:21 ` Jesper Dahl Nyerup
2014-02-18 19:48 ` Jesper Dahl Nyerup
2014-02-18 19:51 ` Jesper Dahl Nyerup
2014-02-21 12:44 ` Karel Zak
2014-02-23 19:20 ` Jesper Dahl Nyerup [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=20140223191959.GA3103@one.com \
--to=nyerup@one.com \
--cc=kzak@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox