Follow up:
If the project at hand causes too many issues, I can work on something
else. I am really just looking for something that I can get started on. If
there is a better alternative, then I would like to do that.
Cheers
Charlie
On Fri, Apr 6, 2018 at 6:19 PM, Charlie Sale
wrote:
>
> John
John
| What problem do you have with assigning your copyright to the FSF?
I don't actually have an issue with this. I don't know what was said
to indicate otherwise (there were indeed many off topic posts).
I am, however, having some issues with running Debian GNU/Hurd on
qemu.
Here is what I h
I don’t really think this is relevant to the topic at hand (Charlie’s personal
introduction), so perhaps a new thread would be best..
What problem do you have with assigning your copyright to the FSF?
--
John M. Harris, Jr.
Splentity Software
On Thursday, April 5, 2018 8:17:59 PM EDT Brent W.
On Thu, Apr 5, 2018 at 7:27 PM, Samuel Thibault
wrote:
> Brent W. Baccala, le jeu. 05 avril 2018 19:06:23 -0400, a ecrit:
>
> Yes, Mach is
> sort of an exception, because it was merely the ground for the whole
> kernel. But being BSD-licenced, it was not posing problems for future
> re-licensing
Brent W. Baccala, le jeu. 05 avril 2018 19:06:23 -0400, a ecrit:
> It sure seems that copyright exceptions are made for big pieces of code (Mach,
> LWIP), but not for contributions from individual developers.
You're again FUD-ing here.
There is a huge difference between easy-to-replace contributi
On Thu, Apr 5, 2018 at 6:53 PM, Samuel Thibault
wrote:
> Brent W. Baccala, le jeu. 05 avril 2018 18:42:24 -0400, a ecrit:
>
> > that the Debian maintainers have threatened to drop us completely unless
> we get
> > our code upstreamed into the main glibc code base.
>
> Nope. That never happened, y
Samuel Thibault, le ven. 06 avril 2018 00:53:39 +0200, a ecrit:
> What did happen is that upstream glibc said they'd really want to have
> glibc master actually build on the Hurd (and even cross-build, which is
> not the harder part) so that they can do build tests while revamping the
> code. That
Brent W. Baccala, le jeu. 05 avril 2018 18:42:24 -0400, a ecrit:
> Also, I should mention that a major issue on the mailing list for the last two
> months has been upstreaming glibc.
You are FUD-ing a lot here.
> It's again related to how we interact with Debian.
Nope, not at all.
> There are s
On Thu, Apr 5, 2018 at 11:20 AM, Charlie Sale
wrote:
> Hey Brent
>
> I would be willing to help with that project. I'll see what I can do to
> contribute.
>
> You said that you had some code written. Where can I find it? Is it in a
> branch on the main tree?
>
No, unfortunately. Part of the rea
Hello,
Charlie Sale, le jeu. 05 avril 2018 15:20:10 +, a ecrit:
> I tried running Debian GNU/Hurd in qemu, but I had some major troubles
> with that (keyboard didn't work at all).
That's very surprising since that's what people would usually use. How
did you start it exactly? Which version o
Hey Brent
I would be willing to help with that project. I'll see what I can do to
contribute.
You said that you had some code written. Where can I find it? Is it in a
branch on the main tree?
Also, would you recommend developing in a GNU/Hurd environment as opposed
to a GNU/Linux environment? I
Charlie -
Welcome to Hurd!
I'm not sure what you consider a small task. Perhaps you could look at my
March 9th email to this list, entitled "RFC: kernel trace facility".
Briefly, I want to instrument the kernel so that we can trace the messages
going to and from a particular task. Our current w
12 matches
Mail list logo
