From: Georg Potthast 2 <nospam@georgpotthast.de>
To: ELKS <Linux-8086@vger.kernel.org>
Subject: Re: [RFC] Taking over dev86
Date: Sat, 25 Feb 2017 13:21:58 +0100 (CET) [thread overview]
Message-ID: <2324326.47464.1488025319065@communicator.strato.com> (raw)
In-Reply-To: <CACpuWUnH1+iSE34PC=gaP5HU5GXBKX3YkehnPWy_BU4bSsVMQw@mail.gmail.com>
bcc is part of the repo of most major Linux distributions. I would suggest to contact the maintainers of the packages in these repos to see which code base they use to generate the packages and what their comments are regarding this plan.
Using an optimising compiler to compile the ELKS kernel would probably cut its size in half. So selecting a different compiler for ELKS would make sense.
Georg
> Marc-François LUCCA-DANIAU <mfld.fr@gmail.com> hat am 24. Februar 2017 um 23:05 geschrieben:
>
>
> No, sorry, Seabios does not depend on dev86.
> That is actually vgabios, also used by QEMU.
>
> MFLD
>
>
> 2017-02-24 22:59 GMT+01:00 Marc-François LUCCA-DANIAU <mfld.fr@gmail.com>:
> > Has lkundrak also stopped to respond to direct mail ?
> >
> > Today his repository looks the one that is referenced as the master in
> > some distributions, at least in their respective build systems. So
> > this takeover should be advertised to their respective maintainers
> > through their ticket systems.
> >
> > It also seems to me that some projects still use dev86 in addition to
> > ELKS, like the coreboot / Seabios, so indirectly some important others
> > like QEMU... therefore I would not takeover without discuting a bit
> > with that teams.
> >
> > MFLD
> >
> >
> > 2017-02-24 22:36 GMT+01:00 Jody Bruchon <jody@jodybruchon.com>:
> >> From my perspective, it appears that lkundrak on Github has abandoned dev86;
> >> there hasn't been a commit or a code pull request accepted to that repo in
> >> nearly two years and lkundrak is not participating in any issue reports or
> >> pull request discussions either. I am considering converting my Github fork
> >> of dev86 into a normal repository and considering my repository to be the
> >> official one for the dev86 project.
> >>
> >> Does anyone see any reason that I shouldn't perform this "hostile takeover"
> >> of dev86? I'd like to hear everyone's thoughts.
> >>
> >> -Jody
> >> --
> >> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> >> the body of a message to majordomo@vger.kernel.org
> >> More majordomo info at http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-02-25 12:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 21:36 [RFC] Taking over dev86 Jody Bruchon
[not found] ` <CACpuWUks3rejCyrbrsFFuxDEKqU6FXAqJ0iYtYxHcHVJzgqFzw@mail.gmail.com>
2017-02-24 22:05 ` Marc-François LUCCA-DANIAU
2017-02-25 12:21 ` Georg Potthast 2 [this message]
2017-02-25 22:43 ` David Given
2017-02-27 15:01 ` Alan Cox
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=2324326.47464.1488025319065@communicator.strato.com \
--to=nospam@georgpotthast.de \
--cc=Linux-8086@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