From: Florian Weimer <fweimer@redhat.com>
To: Vivek Dasmohapatra <vivek@collabora.com>
Cc: Vivek Das Mohapatra via Gnu-gabi <gnu-gabi@sourceware.org>,
Mark Wielaard <mark@klomp.org>
Subject: Re: ABI document
Date: Tue, 30 Aug 2022 14:12:22 +0200 [thread overview]
Message-ID: <87zgfm3p7d.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <a97175af-4ba7-a3fc-1601-dc6b8946d1f9@collabora.com> (Vivek Dasmohapatra's message of "Tue, 30 Aug 2022 12:55:38 +0100")
* Vivek Dasmohapatra:
> On 25/08/2022 09:11, Florian Weimer wrote:
>> * Vivek Das Mohapatra via Gnu-gabi:
>>
>>> Right - I dropped Jakub a line last week and I haven't seen a response
>>> either way: Could someone with commit access apply the attached patches?
>>
>>> [2. text/x-diff; 0001-Document-GNU-extensions-to-ELF-related-to-loading-an.patch]
>>> [3. text/x-diff; 0002-Add-prelink-documentation.patch]
>> I've applied these patches and added links to the overview page at:
>> <https://sourceware.org/gnu-gabi/>
>> Thanks a lot for your contribution!
>
> No problem. I've not had any significant time to look at glibc over
> the last several months - other things at work took priority - but I
> hope to jump back onto the dlmopen/RTLD_SHARED work again soon.
Sure, looking forward to that. One more thing:
It was pointed out to me that we did not discuss licensing. D'oh!
Are you okay with releasing your documentation under the ISC license
variant called 0BSD?
| Copyright The GNU Toolchain Authors.
|
| Permission to use, copy, modify, and/or distribute this software for any
| purpose with or without fee is hereby granted.
|
| THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
| WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
| MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
| ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
| WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
| ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
| OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
I'll also ask if we can release Jakub's document under the same license.
Thanks,
Florian
next prev parent reply other threads:[~2022-08-30 12:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 11:47 Florian Weimer
2020-07-29 11:53 ` Mark Wielaard
2020-07-29 12:15 ` H.J. Lu
2020-07-29 12:22 ` Florian Weimer
2020-08-14 9:51 ` Vivek Das Mohapatra
2020-08-14 10:58 ` Mark Wielaard
2020-08-14 11:33 ` Vivek Das Mohapatra
2020-08-14 15:17 ` Mark Wielaard
2020-08-27 16:52 ` Vivek Das Mohapatra
2020-08-31 12:54 ` Florian Weimer
2020-09-02 17:29 ` Vivek Das Mohapatra
2020-09-08 12:09 ` Vivek Das Mohapatra
2020-09-16 13:57 ` Vivek Das Mohapatra
2020-09-21 13:03 ` Florian Weimer
2020-09-21 12:36 ` Florian Weimer
2020-11-27 15:40 ` Vivek Das Mohapatra
2020-11-30 17:36 ` Florian Weimer
2020-12-09 16:59 ` Vivek Das Mohapatra
2022-08-25 8:11 ` Florian Weimer
2022-08-25 15:38 ` Carlos O'Donell
2022-08-30 11:55 ` Vivek Dasmohapatra
2022-08-30 12:12 ` Florian Weimer [this message]
2022-08-30 15:17 ` Vivek Dasmohapatra
2020-07-29 12:56 ` Jose E. Marchesi
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=87zgfm3p7d.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=gnu-gabi@sourceware.org \
--cc=mark@klomp.org \
--cc=vivek@collabora.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).