From: Junio C Hamano <junkio@cox.net>
To: "Peter Eriksen" <s022018@student.dtu.dk>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Rename safe_strncpy() to strlcpy().
Date: Sat, 24 Jun 2006 22:29:30 -0700 [thread overview]
Message-ID: <7vd5cxzttx.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060624140124.GA1323@ebar092.ebar.dtu.dk> (Peter Eriksen's message of "Sat, 24 Jun 2006 16:01:25 +0200")
"Peter Eriksen" <s022018@student.dtu.dk> writes:
> This cleans up the use of safe_strncpy() even more. Since it has the
> same semantics as strlcpy() use this name instead.
> ---
>
> I've introduced a NO_STRLCPY variable in the Makefile. What do
> you think about this?
No strong preference -- I can go with either name. But people
with more BSD exposure than I am are probably used to see this
function as strlcpy(), so if that is the case let's use this
patch.
Thanks.
prev parent reply other threads:[~2006-06-25 5:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-24 14:01 [PATCH] Rename safe_strncpy() to strlcpy() Peter Eriksen
2006-06-25 5:29 ` Junio C Hamano [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=7vd5cxzttx.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=s022018@student.dtu.dk \
/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;
as well as URLs for NNTP newsgroup(s).