linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze-mcycREo4Un4@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
	<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [patch] stpcpy.3, stpncpy.3: Correct history
Date: Thu, 8 May 2014 13:23:56 +0200	[thread overview]
Message-ID: <20140508112356.GA22640@iris.usta.de> (raw)
In-Reply-To: <CAKgNAkifRNL+1KTa1LrRgJGn7dYUYvf8N5n2Q8V5+0RFXZatvQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hi Michael,

Michael Kerrisk (man-pages) wrote on Thu, May 08, 2014 at 11:55:36AM +0200:
> On Wed, May 7, 2014 at 10:33 PM, Ingo Schwarze <schwarze-mcycREo4Un4@public.gmane.org> wrote:
>> Michael Kerrisk (man-pages) wrote on Fri, May 02, 2014 at 03:58:36PM +0200:

>>> the patch seems more or less okay to me, but given that The AmigaDOS
>>> compiler is the merely the oldest instance you could find, I'd prefer
>>> a slightly more open wording.
>>> How would this be:
>>>
>>> [[
>>> --- a/man3/stpcpy.3
>>> +++ b/man3/stpcpy.3
>>> @@ -76,9 +76,11 @@ function is thread-safe.
>>>  .SH CONFORMING TO
>>>  This function was added to POSIX.1-2008.
>>>  Before that, it was not part of
>>> -the C or POSIX.1 standards, nor customary on UNIX systems, but was not a
>>> -GNU invention either.
>>> -Perhaps it came from MS-DOS.
>>> +the C or POSIX.1 standards, nor customary on UNIX systems.
>>> +It first appeared at least as early as 1986,
>>> +in the Lattice C AmigaDOS compiler,
>>> +then in the GNU fileutils and GNU textutils in 1989,
>>> +and in the GNU C library until 1992.

> Just fixed: s/until/in/

Actually, what i intended to express with that "until" was:

  "in the GNU C library at least as early as 1992"

Glibc development started in 1987.  Clearly glibc didn't have stpcpy
before 1989, or early textutils/fileutils wouldn't have had their
own copy with a 1989 FSF Copyright.  The glibc ChangeLog says
Roland McGrath fixed a bug in stpcpy in 1992, and *after that*,
the file has a 1992 FSF Copyright.

That doesn't strictly exclude stpcpy may have appeared in glibc
in 1989, 1990, or 1991.

Yours,
  Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2014-05-08 11:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-24  0:37 [patch] stpcpy.3, stpncpy.3: Correct history Ingo Schwarze
     [not found] ` <20140224003705.GB28413-1ywcXMbTzNIuZeo0DBJMuQ@public.gmane.org>
2014-05-02 13:58   ` Michael Kerrisk (man-pages)
     [not found]     ` <5363A48C.7060709-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-05-07 20:33       ` Ingo Schwarze
     [not found]         ` <20140507203300.GM3365-1ywcXMbTzNIuZeo0DBJMuQ@public.gmane.org>
2014-05-08  9:55           ` Michael Kerrisk (man-pages)
     [not found]             ` <CAKgNAkifRNL+1KTa1LrRgJGn7dYUYvf8N5n2Q8V5+0RFXZatvQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-08 11:23               ` Ingo Schwarze [this message]
     [not found]                 ` <20140508112356.GA22640-1ywcXMbTzNIuZeo0DBJMuQ@public.gmane.org>
2014-05-08 13:02                   ` Michael Kerrisk (man-pages)

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=20140508112356.GA22640@iris.usta.de \
    --to=schwarze-mcycreo4un4@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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;
as well as URLs for NNTP newsgroup(s).