public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: "Andries E. Brouwer" <aeb@cwi.nl>
Cc: linux-man <linux-man@vger.kernel.org>,
	"G. Branden Robinson" <g.branden.robinson@gmail.com>,
	groff <groff@gnu.org>
Subject: Re: Linux man-pages prehistory
Date: Thu, 15 Dec 2022 23:15:32 +0100	[thread overview]
Message-ID: <99a380d9-a352-cf79-4864-2636d33b98f0@gmail.com> (raw)
In-Reply-To: <20221215200819.GA178852@if>


[-- Attachment #1.1: Type: text/plain, Size: 2182 bytes --]

Hi Andries!

On 12/15/22 21:08, Andries E. Brouwer wrote:
> On Thu, Dec 15, 2022 at 04:24:31PM +0100, Alejandro Colomar wrote:
>> Hi all!
>>
>> I'm pleased to announce that there's a new branch in the git repository,
>> named 'prehistory', which covers exactly that.
> 
> Good! I have one question: did you preserve the time stamps?

Initially I didn't, but I amended the commits to use the timestamp of the 
tarball as the author date.

I did it by copying the timestamp from the website by hand, so a timezone offset 
may be present, but I guess that's better than nothing.

You can check the branch here :)
<https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/log/?h=prehistory>

Here's a sample:


$ git log --pretty=fuller -2 prehistory
commit 9e0fdb0c0192079e5847f49832374ea28b5ad436 (HEAD -> prehistory, 
korg/prehistory)
Author:     Krónos <Krónos@Sāturnus>
AuthorDate: Mon Oct 11 00:00:00 1993 +0100
Commit:     Alejandro Colomar <alx@kernel.org>
CommitDate: Thu Dec 15 23:09:38 2022 +0100

     man-pages 1.0

     man-pages-1.1 seems to be missing.  :/

     Link: <https://www.win.tue.nl/~aeb/ftpdocs/linux-local/manpages.archive/>
     Signed-off-by: Alejandro Colomar <alx@kernel.org>

commit 3c23040573650f36a3f2778a3629f4ae7e6c10ab
Author:     Krónos <Krónos@Sāturnus>
AuthorDate: Mon Nov 29 00:00:00 1993 +0100
Commit:     Alejandro Colomar <alx@kernel.org>
CommitDate: Thu Dec 15 23:09:38 2022 +0100

     man-pages 1.2

     Link: <https://www.win.tue.nl/~aeb/ftpdocs/linux-local/manpages.archive/>
     Signed-off-by: Alejandro Colomar <alx@kernel.org>

> 
>> P.S.:  Andries, do you know anything about 1.1?  There's the announce in
>> your ftp server, but the tarball is missing.
> 
> If man-pages-1.1.tar.gz is missing that means I didnt have it.
> In fact I see time stamps in 1993 for those early files,
> but 2004 for man-pages-1.1-announced, so I guess I searched
> for man-pages-1.1 at that time and found only the announcement.

Yep, that was my guess.  Well, we got enough for most archeology purposes.

Cheers,
Alex

> 
> Andries

-- 
<http://www.alejandro-colomar.es/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2022-12-15 22:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 15:24 Linux man-pages prehistory Alejandro Colomar
2022-12-15 15:25 ` Alejandro Colomar
2022-12-15 17:47 ` Alejandro Colomar
2022-12-15 20:08 ` Andries E. Brouwer
2022-12-15 22:15   ` Alejandro Colomar [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=99a380d9-a352-cf79-4864-2636d33b98f0@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=aeb@cwi.nl \
    --cc=g.branden.robinson@gmail.com \
    --cc=groff@gnu.org \
    --cc=linux-man@vger.kernel.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