The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: arrigo@alchemistowl.org (Arrigo Triulzi)
Subject: [TUHS] History of exploits - request for authors
Date: Fri, 29 Dec 2017 12:14:14 +0100	[thread overview]
Message-ID: <30BA09E9-C575-4205-B383-68EA6D3D4F1C@alchemistowl.org> (raw)
In-Reply-To: <20171219012525.GB11683@mcvoy.com>

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

On 19 Dec 2017, at 02:25, Larry McVoy <lm at mcvoy.com> wrote:
> So the only one I was involved in was the CVS hack to the Linux kernel
> source tree.  This was back in the early 2000's and the kernel used
> my SCM system, BitKeeper, but there were people who didn't like the 
> license.  We built an exporter that exported the history to CVS (it
> was a pretty nice exporter, on a per file basis it would find the 
> longest path through a DAG and export that since CVS was straight
> line, not a DAG.)

Personally I believe it would make a fine historical article for the next issue (17 is out now with 34C3).

Would you be willing to write it up? With enough articles we might even pull a “history issue”!

Arrigo



      parent reply	other threads:[~2017-12-29 11:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-18 10:31 Arrigo Triulzi
2017-12-19  1:08 ` Dave Horsfall
2017-12-19 20:17   ` Derek Fawcus
2017-12-19 20:32     ` Ron Natalie
2017-12-20  2:22       ` Dave Horsfall
2017-12-19 23:45     ` Dave Horsfall
2017-12-29 11:22     ` Arrigo Triulzi
2017-12-19 20:25   ` Derek Fawcus
2017-12-19  1:25 ` Larry McVoy
2017-12-20  0:01   ` Nemo
2017-12-29 11:14   ` Arrigo Triulzi [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=30BA09E9-C575-4205-B383-68EA6D3D4F1C@alchemistowl.org \
    --to=arrigo@alchemistowl.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).