From: "menon.nishanth@gmail.com" <menon.nishanth@gmail.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: lots of inaccurate references to "FileName: include/asm-arm ..."
Date: Tue, 4 Dec 2012 14:59:18 -0600 [thread overview]
Message-ID: <CAGo_u6q6N3pz=32hrs86Xkew2GiTdWMgwng89WrpAccDV0N5uw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1212041551300.3794@oneiric>
On Tue, Dec 4, 2012 at 2:53 PM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> On Tue, 4 Dec 2012, Robert P. J. Day wrote:
>
>> if i don't hear differently, i can submit a patch tomorrow. as you
>> can see, almost all of that content is arm-related:
>>
>> arch/arm/mach-omap/devices-gpmc-nand.c: * FileName: arch/arm/boards/omap/devices-gpmc-nand.c
>
> simple aesthetic question for this cleanup. here's the top of one
> of those sample files:
>
> /**
> * @file
> * @brief GPMC specific NAND devices
> *
> * FileName: arch/arm/boards/omap/devices-gpmc-nand.c
> *
> */
> /*
> * (C) Copyright 2006-2008
> * Texas Instruments, <www.ti.com>
> * Nishanth Menon <x0nishan@ti.com>
> ... snip ...
>
> what would you like the final result to be? collapse the two
> comment blocks into one? just show me what *this* file should end up
> looking like and i'll apply that to all of them.
Seems at least inside TI, we do have a copyright template that has
been aligned on:
/*
* Function of the file
*
* Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.com/
* Nishanth Menon
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License version 2 as
* published by the Free Software Foundation.
* This program is distributed "as is" WITHOUT ANY WARRANTY of any
* kind, whether express or implied; without even the implied warranty
* of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*/
As long as GPL V2 is maintained, I dont see any issues. Adding
historic stuff is nice to have, I usually maintain that esp when
taking code from tarballs to just be sure to provide appropriate
credits.
Regards,
Nishanth Menon
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-12-04 20:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 16:13 Robert P. J. Day
2012-12-04 19:08 ` menon.nishanth
2012-12-04 19:30 ` Robert P. J. Day
2012-12-04 19:36 ` menon.nishanth
2012-12-04 19:49 ` Robert P. J. Day
2012-12-04 20:53 ` Robert P. J. Day
2012-12-04 20:59 ` menon.nishanth [this message]
2012-12-04 21:03 ` Robert P. J. Day
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='CAGo_u6q6N3pz=32hrs86Xkew2GiTdWMgwng89WrpAccDV0N5uw@mail.gmail.com' \
--to=menon.nishanth@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=rpjday@crashcourse.ca \
/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