From: imp@bsdimp.com (Warner Losh)
Subject: [TUHS] Free/NetBSD revision history (was Code bloat)
Date: Thu, 9 Feb 2017 21:17:28 -0700 [thread overview]
Message-ID: <CANCZdfp6qh=TnET_TEj27zbqTOcKrRXartR=8wxNJvW7LnkB1g@mail.gmail.com> (raw)
In-Reply-To: <59edd244efc6fca1609f5707dd39833e@xs4all.nl>
On Thu, Feb 9, 2017 at 4:38 PM, Jacob Goense <dugo at xs4all.nl> wrote:
> That's the thing, it banks on what is publicly available.
A google search finds
https://github.com/jonathangray?tab=repositories
has CVS trees from the 1.1.5 FreeBSD CD-ROM, 386BSD + patchkit and the
csrg sources converted from SCCS to git. Are any of these useful in
filling in the gaps?
Warner
next prev parent reply other threads:[~2017-02-10 4:17 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 3:03 [TUHS] How Unix brings people together, or it's a small Doug McIlroy
2017-02-07 4:06 ` Marc Rochkind
2017-02-07 23:10 ` Clem Cole
2017-02-07 23:38 ` Steve Johnson
2017-02-08 2:55 ` [TUHS] Code bloat (was: How Unix brings people together, or it's a small...) Greg 'groggy' Lehey
2017-02-08 3:47 ` Nick Downing
2017-02-08 3:56 ` Jason Stevens
2017-02-08 8:25 ` Wesley Parish
2017-02-08 9:57 ` Steve Nickolas
2017-02-08 11:21 ` Nick Downing
2017-02-08 11:59 ` [TUHS] Code bloat (was: How Unix brings people together, or it'sa small...) jsteve
2017-02-08 12:24 ` Nick Downing
2017-02-08 12:29 ` [TUHS] Code bloat Jacob Goense
2017-02-08 12:57 ` Nick Downing
2017-02-08 13:10 ` jsteve
2017-02-08 14:10 ` Jacob Goense
2017-02-08 14:34 ` Ron Natalie
2017-02-08 14:43 ` Brantley Coile
2017-02-08 15:09 ` Dan Cross
2017-02-08 15:26 ` Nick Downing
2017-02-08 15:18 ` Jason Stevens
2017-02-08 16:25 ` Tony Finch
2017-02-09 14:03 ` Jacob Goense
2017-02-09 14:41 ` jsteve
2017-02-09 15:03 ` Jacob Goense
2017-02-09 15:08 ` Jason Stevens
2017-02-09 15:30 ` Tony Finch
2017-02-09 16:14 ` Warner Losh
2017-02-09 23:38 ` [TUHS] Free/NetBSD revision history (was Code bloat) Jacob Goense
2017-02-10 4:11 ` Warner Losh
2017-02-10 4:17 ` Warner Losh [this message]
2017-02-08 13:56 ` [TUHS] Code bloat (was: How Unix brings people together, or it's a small...) Paul Ruizendaal
[not found] ` <CAH1jEzZqRPYenwzBbUwFVanA-NVvWMGzYiADVoAXCDOqnUrMrg@mail.gmail.com>
2017-02-09 3:02 ` [TUHS] Fwd: " Nick Downing
2017-02-09 9:19 ` [TUHS] " Paul Ruizendaal
2017-02-09 9:58 ` Michael Kjörling
2017-02-09 10:08 ` Paul Ruizendaal
2017-02-09 16:36 ` Larry McVoy
2017-02-09 16:42 ` Warner Losh
2017-02-09 16:49 ` Larry McVoy
2017-02-09 17:24 ` Steffen Nurpmeso
2017-02-09 17:27 ` [TUHS] offtopic: broadband (redirect from bloat) Larry McVoy
2017-02-09 19:05 ` Steffen Nurpmeso
2017-02-09 22:48 ` Joerg Schilling
2017-02-09 19:54 ` [TUHS] Code bloat (was: How Unix brings people together, Corey Lindsly
2017-02-09 20:08 ` pechter
2017-02-09 20:30 ` Arthur Krewat
2017-02-09 23:47 ` Jacob Goense
2017-02-09 21:06 ` Larry McVoy
2017-02-09 21:02 ` [TUHS] Code bloat (was: How Unix brings people together, or it's a small...) Joerg Schilling
2017-02-09 16:58 ` [TUHS] Code bloat William Pechter
2017-02-09 19:50 ` [TUHS] Code bloat (was: How Unix brings people together, or it's a small...) Clem Cole
2017-02-08 5:37 ` Peter Jeremy
2017-02-08 12:16 ` [TUHS] How Unix brings people together, or it's a small ches@Cheswick.com
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='CANCZdfp6qh=TnET_TEj27zbqTOcKrRXartR=8wxNJvW7LnkB1g@mail.gmail.com' \
--to=imp@bsdimp.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).