From: Trek <trek00@inbox.ru>
To: Harald van Dijk <harald@gigawatt.nl>
Cc: dash@vger.kernel.org
Subject: Re: echo do not print NUL byte
Date: Thu, 21 Jan 2016 02:40:56 +0100 [thread overview]
Message-ID: <20160121024056.5eb1ff04@enterprise> (raw)
In-Reply-To: <56A00AEB.5090606@gigawatt.nl>
On Wed, 20 Jan 2016 23:32:11 +0100
Harald van Dijk <harald@gigawatt.nl> wrote:
> This is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=379227,
> which did get fixed already, but it was after 0.5.8.
happy to see that it is already fixed and sorry for double reporting
next prev parent reply other threads:[~2016-01-21 1:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 21:38 echo do not print NUL byte Trek
2016-01-20 22:19 ` Eric Blake
2016-01-20 22:32 ` Harald van Dijk
2016-01-21 1:40 ` Trek [this message]
2016-01-21 7:18 ` Bastian Bittorf
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=20160121024056.5eb1ff04@enterprise \
--to=trek00@inbox.ru \
--cc=dash@vger.kernel.org \
--cc=harald@gigawatt.nl \
/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