public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <binutils@emagii.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH v6 01/11] DIGEST: LICENSING
Date: Wed, 1 Mar 2023 16:30:14 +0100	[thread overview]
Message-ID: <955abc7b-2f23-a53f-1a74-fb9bd6d2c2e0@emagii.com> (raw)
In-Reply-To: <373d5a6b-a661-1987-8154-c799dfc59ba6@redhat.com>


On 2023-03-01 16:04, Nick Clifton wrote:
> Hi Ulf,
>
>> diff --git a/COPYING-MIT.SUNSHINE b/COPYING-MIT.SUNSHINE
>
> Why is the file called COPYING-MIT.SUNSHINE ?
> (This is mainly curiosity, plus a check to make sure that the
> name is correct).

The license comes from:

http://www.sunshine2k.de/

and I did not modify it.

Maybe it should be named COPYING.www.sunshine2k.de

Should I have a comment on top of the file and enclose
the real license inside?

comment

=====

<contents of license file>

=====


>
>
>> +All content of this website is released under the MIT license as 
>> follows:
>
> What website ?

http://www.sunshine2k.de/


>
> I think that you need to change this line and instead indicate exactly 
> what
> code & documentation is covered by this license.
>
>
>> +The GNU linker contains CRC routines that are used to implement the
>> +DIGEST CRC32/64 commands in the output section.
>
> There are two GNU linkers - ld (aka ld.bfd) and gold (aka ld.gold).  
> Since
> you are not patching gold I would suggest moving the COPYING.LIBRC 
> file into
> the ld/ sub-dirctory.  Or submitting patches for gold as well as ld 
> ... :-)
>
I never used the ld.gold linker.

What is this doing?

> Cheers
>   Nick
>

  reply	other threads:[~2023-03-01 15:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01 14:47 [PATCH v6 0/11 Add support for CRC64 generation in linker binutils
2023-03-01 14:47 ` [PATCH v6 01/11] DIGEST: LICENSING binutils
2023-03-01 15:04   ` Nick Clifton
2023-03-01 15:30     ` Ulf Samuelsson [this message]
2023-03-01 17:15       ` Nick Clifton
2023-03-01 17:19         ` Ian Lance Taylor
2023-03-01 14:47 ` [PATCH v6 02/11] DIGEST: NEWS binutils
2023-03-01 14:57   ` Ulf Samuelsson
2023-03-01 14:47 ` [PATCH v6 03/11] DIGEST: Documentation binutils
2023-03-01 14:47 ` [PATCH v6 04/11] DIGEST: testsuite binutils
2023-03-01 16:48   ` Nick Clifton
2023-03-01 17:33     ` Ulf Samuelsson
2023-03-01 14:47 ` [PATCH v6 05/11] DIGEST: ldlex.l binutils
2023-03-01 14:47 ` [PATCH v6 06/11] DIGEST: ldgram.y binutils
2023-03-01 14:47 ` [PATCH v6 07/11] DIGEST: ldmain.c binutils
2023-03-01 14:47 ` [PATCH v6 08/11] DIGEST: ldlang.*: add timestamp binutils
2023-03-01 14:47 ` [PATCH v6 09/11] DIGEST: calculation binutils
2023-03-01 14:47 ` [PATCH v6 10/11] DIGEST: Makefile.* binutils
2023-03-01 14:47 ` [PATCH v6 11/11] Build ldint binutils
2023-03-01 14:53 ` [PATCH v6 0/11 Add support for CRC64 generation in linker Ulf Samuelsson

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=955abc7b-2f23-a53f-1a74-fb9bd6d2c2e0@emagii.com \
    --to=binutils@emagii.com \
    --cc=binutils@sourceware.org \
    --cc=nickc@redhat.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).