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 12:08:58 +0200 [thread overview]
Message-ID: <20130807120858.726f6a62@lilith> (raw)
In-Reply-To: <20130807073319.4D388380DE1@gemini.denx.de>
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.
prev parent reply other threads:[~2013-08-07 10:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
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=20130807120858.726f6a62@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 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.