From: Oleh Derevenko <oleh.derevenko@gmail.com>
To: DJ Delorie <dj@redhat.com>
Cc: Joseph Myers <joseph@codesourcery.com>, libc-alpha@sourceware.org
Subject: Re: [RFC 0/1] Contributing a compound object to the libpthread
Date: Tue, 19 Jun 2018 22:39:00 -0000 [thread overview]
Message-ID: <CAC1wWD2dfbu0soBYP+vHx2_zJM36pc-sDwe6Yv5XjE9x_3qEgQ@mail.gmail.com> (raw)
In-Reply-To: <xnvaaelffk.fsf@greed.delorie.com>
Gentlemen,
Thank you for all your suggestions and explanations.
Generally, I understand what you say and I basically knew that. You
explain the standard approach and why it has happened that it is here.
Alas, as I already initially mentioned, for me accepting the standard
approach would be simply resigning everything and staying with fame
only.
Well, I don't have fame either yet.
Now I don't even know why could I think such a huge machine would
adapt for a single person. I wanted to be with the library, but not a
part of the library.
I understand this might look like a parasitic approach, but still... I
supposed there would be something I would be giving back to the
library as well.
I guess, I'll be thinking towards what Adhemerval Zanella and Zack
Weinberg suggested: distributing own library. Thank you, gentlemen,
for that — it might be really a thing I needed to be doing anyway, an
unavoidable step.
May I come here with an announcement when it will be ready?
On Tue, Jun 19, 2018 at 10:55 PM, DJ Delorie <dj@redhat.com> wrote:
> Joseph Myers <joseph@codesourcery.com> writes:
>> And specifically, what I think is the current assignment
>> (/gd/gnuorg/copyright/assign.future on fencepost) says:
>
> Heh, I was trying to avoid scaring anyone off with *actual* legalese,
> but yeah, there are details which IMHO are best left to a lawyer. If
> Oleh has a patent, he probably has a lawyer too.
--
Oleh Derevenko
-- Skype with underscore
next prev parent reply other threads:[~2018-06-19 22:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 23:35 Oleh Derevenko
2018-04-02 23:07 ` Oleh Derevenko
2018-04-03 13:41 ` Ben Hutchings
2018-04-03 20:06 ` Oleh Derevenko
[not found] ` <CAC1wWD0OwFLqUD2uXnavBzfEw=HCRn3fGW54zYfxRozxp8HsyA@mail.gmail.com>
2018-06-15 14:05 ` Oleh Derevenko
2018-06-15 14:31 ` Florian Weimer
2018-06-16 18:37 ` Oleh Derevenko
2018-06-18 13:22 ` Adhemerval Zanella
2018-06-18 19:52 ` Oleh Derevenko
2018-06-18 21:03 ` Adhemerval Zanella
2018-06-18 21:06 ` DJ Delorie
2018-06-18 22:26 ` Oleh Derevenko
2018-06-19 12:07 ` Adhemerval Zanella
2018-06-19 12:42 ` Oleh Derevenko
2018-06-19 13:09 ` Adhemerval Zanella
2018-06-19 15:36 ` Patrick McGehearty
2018-06-19 16:28 ` DJ Delorie
2018-06-19 16:52 ` Zack Weinberg
2018-06-19 19:26 ` Joseph Myers
2018-06-19 19:55 ` DJ Delorie
2018-06-19 22:39 ` Oleh Derevenko [this message]
2018-06-20 13:14 ` Carlos O'Donell
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=CAC1wWD2dfbu0soBYP+vHx2_zJM36pc-sDwe6Yv5XjE9x_3qEgQ@mail.gmail.com \
--to=oleh.derevenko@gmail.com \
--cc=dj@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).