public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Thorsten Glaser <tg@mirbsd.de>
To: linux-m68k@vger.kernel.org
Subject: Re: 68000 patches (Atari ST platform)
Date: Thu, 15 Sep 2011 11:45:13 +0000 (UTC)	[thread overview]
Message-ID: <loom.20110915T134159-512@post.gmane.org> (raw)
In-Reply-To: CAOmrzk+sqAzh48zXOKQ06iRhceJMTZvPJiDDTASgmT1Qv1B-7Q@mail.gmail.com

Michael Schmitz <schmitzmic <at> googlemail.com> writes:

> ataboot used to be part of the m68k CVS on kullervo.debian.net but we
> have had to take kullervo offline half a year ago. Christian has
> rebuilt the system but we're still having trouble with the ethernet
> driver in 3.1 (sort of working on this). I'm sure we can clone the
> m68k CVS off kullervo and set it up somewhere else.

Ah, there they are ;) I’ve NMU’d the m68k bootstraps (Atari, Amiga, VMS,
Mac except where shared with macppc) in Debian to get their source uploaded
to unreleased (since they were removed from unstable), and wondered about
them. (And the packaging is positively ancient, understandably.)

I could host them (I love CVS, after all, *and* I maintain CVS in Debian,
and use it a lot in BSD…) if you want, and can arrange for commit access
for selected people (tell me whom, and I need a PGP trust path) including
mails (with or (default) without diffs sent inline). I can put it on my
box at home (P-233MMX with an actual Hercules Graphics Card, behind ADSL)
or put a separate repo on another box, whatever is your preference.

bye,
//mirabilos

  reply	other threads:[~2011-09-15 11:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-11 23:09 68000 patches (Atari ST platform) Matthias Reis
2011-09-11 23:26 ` Michael Schmitz
2011-09-15 11:45   ` Thorsten Glaser [this message]
2011-09-15 11:53     ` Geert Uytterhoeven
2011-09-16  1:06     ` Michael Schmitz
2011-09-16  8:20       ` Thorsten Glaser

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=loom.20110915T134159-512@post.gmane.org \
    --to=tg@mirbsd.de \
    --cc=linux-m68k@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