From: Bastian Bittorf <bittorf@bluebottle.com>
To: Trek <trek00@inbox.ru>
Cc: dash@vger.kernel.org
Subject: Re: echo do not print NUL byte
Date: Thu, 21 Jan 2016 08:18:04 +0100 [thread overview]
Message-ID: <20160121071804.GF27441@medion.lan> (raw)
In-Reply-To: <20160120223850.25cdf852@enterprise>
* Trek <trek00@inbox.ru> [21.01.2016 07:06]:
> included in http://www.trek.eu.org/devel/naive/naive-0.0.2.tar.gz
interesting! can you switch to git or another CVS?
bye, bastian
prev parent reply other threads:[~2016-01-21 7:26 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
2016-01-21 7:18 ` Bastian Bittorf [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=20160121071804.GF27441@medion.lan \
--to=bittorf@bluebottle.com \
--cc=dash@vger.kernel.org \
--cc=trek00@inbox.ru \
/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.