public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] Merging multiple ARM start.S files, what about copyright lines?
Date: Wed, 7 Aug 2013 09:23:18 +0200	[thread overview]
Message-ID: <20130807092318.1fd9bab5@lilith> (raw)

Hello all,

I am continuing my effort to merge all arch/arm/cpu/**/start.S files
into a single arch/arm/cpu/start.S one, keeping as little cpu-specific
code as I can.

However, there is a non-technical issue: there are many copyright lines
in the files, plus in some case "inherited copyright" when the file's
code comes from some other source. Many of these copyright lines are
repeated across series of CPUs.

How should I handle this in the final file?

The quickest, and preferred by me, way would be to create the new file
with all copyright lines simply "merged", and rely on the git repo to
find out who contributed what.

I could also put one "copyright lines block" per original start.S file.
That would help make quite a big copyrights section.

And there are certainly many other ways I could do it.

But IANAL (AIDPOOTV, either) and I prefer gathering some input from
people who have more experience in this area than I do.

So... any advice welcome on how I should proceed on this point. :)

Amicalement,
-- 
Albert.

             reply	other threads:[~2013-08-07  7:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-07  7:23 Albert ARIBAUD [this message]
2013-08-07  7:33 ` [U-Boot] Merging multiple ARM start.S files, what about copyright lines? Wolfgang Denk
2013-08-07 10:08   ` Albert ARIBAUD

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=20130807092318.1fd9bab5@lilith \
    --to=albert.u.boot@aribaud.net \
    --cc=u-boot@lists.denx.de \
    /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