From: Mario Frasca <mfrasca@zonnet.nl>
To: Harley Laue <losinggeneration@gmail.com>
Cc: linux-8086@vger.kernel.org
Subject: Re: [ELKS] Should we resume ELKS development?
Date: Sun, 15 May 2011 11:53:53 +0200 [thread overview]
Message-ID: <20110515095353.GA2322@croese.home.bogus> (raw)
In-Reply-To: <BANLkTin7gjxkkZmJu1gv5d-Aq+ZexDUV=g@mail.gmail.com>
On 2011-0510 14:44:19, Harley Laue wrote:
> jody@jodybruchon.com wrote:
> > I have taken the liberty of downloading as much ELKS-related code and
> > materials as possible, and I am prepared to set up a Git repository for
> > ELKS if enough interest in such a thing exists.
>
> Personally I did a git cvsimport almost two years ago (not much really
> came from that though), but an official Git repo for some of the
> current CVS trees would be even more ideal :)
>
> > Thanks in advance, and I'm looking forward to hearing from everyone once
> > more.
> > Jody Bruchon
hi here,
I'm an old-time contributor to parts of ELKS. not the kernel, though.
Harley, when you say git, you don't mean github?
(I like git and the 'fork' freedom it gives, and I like github).
I see this one on sourceforge:
git://elks.git.sourceforge.net/gitroot/elks/elks
as on github, one just needs an account to start a own fork.
sounds VERY useful, and as for "official", I would let practice show
which is the leading line. a few years ago some old contributors also
tried to revive the project, but after some discussion somehow we all
dropped the idea. maybe had to do with difficulty to get write access
to the repository, I can't remember. had git existed at the time,
maybe things could have moved better. let's see who is still around!
my PPC640 is still waiting (but diskettes have become rare)! :)
MF
--
lapide al cimitero:
qui giace un ateo
vestito di tutto punto
senza un posto dove andare.
next prev parent reply other threads:[~2011-05-15 9:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 5:51 [ELKS] Should we resume ELKS development? jody
2011-04-11 6:18 ` Gregg Levine
2011-05-10 19:44 ` Harley Laue
2011-05-15 3:13 ` Jody
2011-05-15 9:53 ` Mario Frasca [this message]
2011-05-16 20:50 ` Harley Laue
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=20110515095353.GA2322@croese.home.bogus \
--to=mfrasca@zonnet.nl \
--cc=linux-8086@vger.kernel.org \
--cc=losinggeneration@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