All of lore.kernel.org
 help / color / mirror / Atom feed
* [U-Boot] Merging multiple ARM start.S files, what about copyright lines?
@ 2013-08-07  7:23 Albert ARIBAUD
  2013-08-07  7:33 ` Wolfgang Denk
  0 siblings, 1 reply; 3+ messages in thread
From: Albert ARIBAUD @ 2013-08-07  7:23 UTC (permalink / raw)
  To: u-boot

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.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [U-Boot] Merging multiple ARM start.S files, what about copyright lines?
  2013-08-07  7:23 [U-Boot] Merging multiple ARM start.S files, what about copyright lines? Albert ARIBAUD
@ 2013-08-07  7:33 ` Wolfgang Denk
  2013-08-07 10:08   ` Albert ARIBAUD
  0 siblings, 1 reply; 3+ messages in thread
From: Wolfgang Denk @ 2013-08-07  7:33 UTC (permalink / raw)
  To: u-boot

Dear Albert,

In message <20130807092318.1fd9bab5@lilith> you wrote:
> 
> 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.

Yes, this makes sense.

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

This would not add any real information, but just blow up the file.

My vote is going for a merge.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
The easiest way to figure the cost of living is to take  your  income
and add ten percent.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [U-Boot] Merging multiple ARM start.S files, what about copyright lines?
  2013-08-07  7:33 ` Wolfgang Denk
@ 2013-08-07 10:08   ` Albert ARIBAUD
  0 siblings, 0 replies; 3+ messages in thread
From: Albert ARIBAUD @ 2013-08-07 10:08 UTC (permalink / raw)
  To: u-boot

Hi Wolfgang,

On Wed, 07 Aug 2013 09:33:18 +0200, Wolfgang Denk <wd@denx.de> wrote:

> Dear Albert,
> 
> In message <20130807092318.1fd9bab5@lilith> you wrote:
> > 
> > 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.
> 
> Yes, this makes sense.
> 
> > I could also put one "copyright lines block" per original start.S file.
> > That would help make quite a big copyrights section.

s/help// :)

> This would not add any real information, but just blow up the file.
> 
> My vote is going for a merge.

Thanks.

> Best regards,
> 
> Wolfgang Denk

Amicalement,
-- 
Albert.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2013-08-07 10:08 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-08-07  7:23 [U-Boot] Merging multiple ARM start.S files, what about copyright lines? Albert ARIBAUD
2013-08-07  7:33 ` Wolfgang Denk
2013-08-07 10:08   ` Albert ARIBAUD

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.