The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jacob.ritorto@gmail.com (Jacob Ritorto)
Subject: [TUHS] Pristine version of 2.11BSD
Date: Sat, 19 Dec 2015 18:55:41 -0500	[thread overview]
Message-ID: <CAHYQbfAGPRB5WW7qUcChQuDp=LNVk+72b__AU=ObTStemc3Zqw@mail.gmail.com> (raw)
In-Reply-To: <m2si2y3vpe.fsf@athene.hamartun.priv.no>

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

My $0.02:  Stop at exactly where you know it's still completely clean and
document well (i.e. this email copied into a README somewhere with the
distro) what's blocking you.  If you proceed with force, it maligns the
goal, here, which was stated as "pristine."  Many, many thanks for the push
this far, however!

--jake


On Sat, Dec 19, 2015 at 5:44 PM, Tom Ivar Helbekkmo <tih at hamartun.priv.no>
wrote:

> I wrote:
>
> > For what it's worth, I've begun.  So far, I've worked backward from
> > patchlevel 195 to 177.  I've had to patch files forward from 2.10.1 a
> > couple of times, and that's gone without a hitch.
>
> Ran into trouble with patch 141.  The /usr/src/bin/ld.c file from 2.10.1
> is too old; patches from between that and the initial 2.11 are missing,
> and the file gets deleted and replaced at a later level of 2.11 patches,
> breaking the history.  Patch 141 uncovers the problem.
>
> I can make the patches work, of course - but it means that for much of
> the resulting 2.11 history, /usr/src/bin/ld.c will be wrong.
>
> -tih
> --
> Elections cannot be allowed to change anything.  --Dr. Wolfgang Schäuble
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20151219/46b0b44a/attachment.html>


  reply	other threads:[~2015-12-19 23:55 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-14  9:51 [TUHS] 2.11BSD mirror Warren Toomey
2015-12-14 10:30 ` Lars Brinkhoff
2015-12-14 11:01   ` Warren Toomey
2015-12-16  0:02     ` Jacob Goense
2015-12-16  0:19       ` Warren Toomey
2015-12-16  0:37         ` Jacob Goense
2015-12-16  4:37           ` arnold
2015-12-17 22:43       ` [TUHS] Pristine version of 2.11BSD Warren Toomey
2015-12-17 22:45         ` Warner Losh
2015-12-18  2:49           ` Random832
2015-12-18  0:34         ` Mary Ann Horton
2015-12-18 14:02           ` Jeremy C. Reed
2015-12-18 22:31             ` Warren Toomey
2015-12-18 11:04         ` Tom Ivar Helbekkmo
2015-12-19 14:16           ` Tom Ivar Helbekkmo
2015-12-19 22:44             ` Tom Ivar Helbekkmo
2015-12-19 23:55               ` Jacob Ritorto [this message]
2015-12-20  2:41                 ` Random832
2015-12-20 12:12                   ` Jacob Ritorto
2015-12-20 21:37               ` Jacob Goense
2015-12-21  9:19                 ` Tom Ivar Helbekkmo
2015-12-21 14:06                   ` Jacob Goense
2015-12-21 19:05                     ` Peter Jeremy
2015-12-21 22:30                       ` Jacob Goense
2015-12-22  0:44                         ` Warren Toomey
2015-12-22 21:12                     ` Dave Horsfall
2015-12-18 13:27         ` Tom Ivar Helbekkmo
2015-12-18 13:50           ` Tom Ivar Helbekkmo

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='CAHYQbfAGPRB5WW7qUcChQuDp=LNVk+72b__AU=ObTStemc3Zqw@mail.gmail.com' \
    --to=jacob.ritorto@gmail.com \
    /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).