The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: schily@schily.net (Joerg Schilling)
Subject: [TUHS] Claim your early Unix contributions on GitHub
Date: Wed, 30 Mar 2016 15:44:20 +0200	[thread overview]
Message-ID: <56fbd834.kYVz71Do4YCh3a8S%schily@schily.net> (raw)
In-Reply-To: <56FBD062.3060009@aueb.gr>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2626 bytes --]

Diomidis Spinellis <dds at aueb.gr> wrote:

> On 30/03/2016 15:31, Joerg Schilling wrote:
> > Given that using git enforces a loss of meta data, is there a chance to get
> > the SCCS history for older UNIX versions?
>
> I've tried to incorporate the SCCS meta data in the Git commits.  Where 
> that was not possible I added a header-like line in the Git commit message.
>
> The BSD CSRG SCCS data are available on the four CD set compiled by 
> Marshall Kirk McKusick https://www.mckusick.com/csrg/.
>
> I don't know of any other SCCS data openly available.  If anyone has 
> such data, I'd appreciate a copy.

I know of no other SCCS data, but let me make a remark that results from a 
recent discussion with Kirk Mckusick:

Kirk told me that the regents of UCB do not like the unmodified (original) SCCS 
history data to be published unless this is done with a written permission.
Currently only Kirk owns such a permission.

Kirk did however aks whether the GIT repo from CSRG would be OK as it contains 
hand made fixes for a disk crash and as it does not use the original meta data.
The result was that there is no problem with a different archive format.

Given that the recent (upcomming **) SCCS history format (SCCSv6) is not the 
original SCCSv4 format that was used in CSRG, it seems that using the hand 
crafted fixed and a conversion to SCCSv6 would be OK as well.

The advantage with the SCCSv6 history format is that you are able to convert it 
back to the SCCSv4 history format via:

	sccs -R cvt -d -V4 .

;-)

I am planning a SCCSv6 variant of the CSRG archives, but I need to manually fix 
the broken history files first. Note that this now may be a bit easier because

	sccs -R val -T

gives better warnings since a few years than the historic sccs did.


Note that a full SCCS history may be very helpful. Last year, I came up with 
some problems in the Bourne Shell and a SCCS history with delta comments from 
around 1983 would have been very helpful to understand some changes that 
introduced bugs.

I also recently was interested in knowing when waitpid() was introduced.

**) upcomming because support for project based commits and network support is 
not yet ready in sccs.

See http://sccs.sourceforge.net/man/sccsfile.4.html for a description of the 
SCCSv6 history format.

Jörg

-- 
 EMail:joerg at schily.net                  (home) Jörg Schilling D-13353 Berlin
       js at cs.tu-berlin.de                (uni)  
       joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/


  reply	other threads:[~2016-03-30 13:44 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-30  7:53 Diomidis Spinellis
2016-03-30 12:31 ` Joerg Schilling
2016-03-30 13:10   ` Diomidis Spinellis
2016-03-30 13:44     ` Joerg Schilling [this message]
2016-03-30 19:17   ` Larry McVoy
2016-03-30 21:07     ` Random832
2016-03-30 23:03       ` Joerg Schilling
2016-03-31  3:20       ` Larry McVoy
2016-03-31  3:34         ` Random832
2016-03-31  3:40           ` Larry McVoy
2016-03-30 23:42     ` Joerg Schilling
2016-03-31  3:54       ` Larry McVoy
2016-03-30 14:25 ` Marc Rochkind
2016-03-30 15:23   ` Joerg Schilling
2016-03-30 19:14     ` Larry McVoy
2016-03-30 15:49   ` Diomidis Spinellis
2016-03-30 16:07     ` Joerg Schilling
2016-03-30 16:29       ` Diomidis Spinellis
2016-03-30 16:14     ` Pat Barron
2016-03-31 21:06       ` Clem Cole
2016-03-31 21:54         ` Ron Natalie
2016-04-01  9:01         ` Diomidis Spinellis
2016-04-01 14:41           ` Clem Cole
2016-04-01 21:00           ` Jeremy C. Reed
2016-04-01 13:06         ` Dave Horsfall
2016-04-01 21:52         ` Pat Barron
2016-03-30 16:30     ` Marc Rochkind
2016-03-30 16:40       ` Joerg Schilling
2016-03-30 16:55       ` John Cowan
2016-03-30 18:28 Norman Wilson
2016-03-30 20:06 ` Ronald Natalie

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=56fbd834.kYVz71Do4YCh3a8S%schily@schily.net \
    --to=schily@schily.net \
    /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).