git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
To: Peter Eriksen <s022018@student.dtu.dk>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Implement safe_strncpy() as strlcpy() and use it more.
Date: Sun, 11 Jun 2006 13:17:43 +0200	[thread overview]
Message-ID: <448BFBD7.60900@lsrfire.ath.cx> (raw)
In-Reply-To: <20060611103358.GB10430@bohr.gbar.dtu.dk>

Peter Eriksen schrieb:
> On Sun, Jun 11, 2006 at 07:15:40PM +0900, YOSHIFUJI Hideaki / ?$B5HF#1QL@ wrote:
>> In article <20060611100628.GA10430@bohr.gbar.dtu.dk> (at Sun, 11 Jun 2006 12:06:28 +0200), "Peter Eriksen" <s022018@student.dtu.dk> says:
>>
>>> I've taken strlcpy() from the OpenBSD CVS without attribution.  Is this
>>> allowed?  If it is, how should it be stated?
>> Please include full copyright information.
> 
> Where should this information go?  Just above the function
> safe_strncpy(), or at the top of path.c?  I believe path.c is GPL, so
> can this be mixed freely with BSD licensed code?  Should I put
> safe_strncpy() into a seperate file as with strlcpy()?

Yes...  Or you could avoid all of this by using a GPL'd version, like
the one from the Linux kernel (in lib/string.c).

René

  reply	other threads:[~2006-06-11 11:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-11 10:06 [PATCH] Implement safe_strncpy() as strlcpy() and use it more Peter Eriksen
2006-06-11 10:15 ` YOSHIFUJI Hideaki / 吉藤英明
2006-06-11 10:33   ` Peter Eriksen
2006-06-11 11:17     ` Rene Scharfe [this message]
2006-06-11 16:45     ` Linus Torvalds

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=448BFBD7.60900@lsrfire.ath.cx \
    --to=rene.scharfe@lsrfire.ath.cx \
    --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).