public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Benno Schulenberg <bensberg@justemail.net>
To: Karel Zak <kzak@redhat.com>
Cc: "Util-Linux" <util-linux@vger.kernel.org>
Subject: Re: [patches] standardizing the error messages "cannot read %s" and "seek on %s failed"
Date: Wed, 09 Oct 2013 12:32:19 +0200	[thread overview]
Message-ID: <1381314739.31245.31854957.68AADCCC@webmail.messagingengine.com> (raw)
In-Reply-To: <20131009094712.GK13559@x2.net.home>


On Wed, Oct 9, 2013, at 11:47, Karel Zak wrote:
>  So I guess we're ready for -rc2, right? (probably tomorrow/Friday)

Yes, for this cycle I'm done.  :)

If I do anything else, it will be just man pages.

Benno

-- 
http://www.fastmail.fm - Choose from over 50 domains or use your own

  reply	other threads:[~2013-10-09 10:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08 15:40 [patches] standardizing the error messages "cannot read %s" and "seek on %s failed" Benno Schulenberg
2013-10-09  9:47 ` Karel Zak
2013-10-09 10:32   ` Benno Schulenberg [this message]
2013-10-09 18:57   ` docs: improve the cal --help [was: standardizing...] Benno Schulenberg
2013-10-11  8:52     ` 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=1381314739.31245.31854957.68AADCCC@webmail.messagingengine.com \
    --to=bensberg@justemail.net \
    --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