From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] Uboot_Header_Modification_by_CVS
Date: Mon, 20 Jan 2014 09:03:15 +0100 [thread overview]
Message-ID: <20140120090315.36a7eeee@lilith> (raw)
In-Reply-To: <82CF479D9040C547849E3005E77F780024B75A@SVFRWEXCH1.ikanos.com>
Hi Arun,
On Mon, 20 Jan 2014 07:11:19 +0000, "Arun K. Varghese"
<avarghes@ikanos.com> wrote:
> Hi,
>
> Issue.
> -------
>
> 1) Downloaded u-boot-2010.09 source code. (u-boot-2010.09.tar.bz2<http://ftp.denx.de/pub/u-boot/u-boot-2010.09.tar.bz2>)
> 2) Some files, have version & header information along with the source code.
>
> Ex:
> 1) In u-boot-2010.09/arch/arm/cpu/ixp/npe/include/IxI2cDrv.h
>
> * @version $Revision: 0.1 $
>
> 2) In u-boot-2010.09/arch/i386/cpu/sc520/sc520_asm.S
>
> * $Revision: 1.2 $
> * $Date: 1999/09/22 12:49:33 $
> * $Author: chipf $
>
> 3) When I do a check in for these files, using CVS, these header information is changed.
> CVS is automatically modifying these headers.
>
> Eg :
>
> In u-boot-2010.09/arch/i386/cpu/sc520/sc520_asm.S
>
> * $Revision: 1.2 $
> * $Date: 1999/09/22 12:49:33 $
> * $Author: chipf $
>
> If I do a check in, it will be changed to
>
> * $Revision: 1.1.1.2 $
> * $Date: 2013/12/16 12:49:33 $
> * $Author: Arun $
>
> Doubts
> ---------
>
> 1. Why only few files have these kind of header information in Uboot repository ?
I suspect that is because only a few files (still) contain any
CVS-specific information, since we're using git, not CVS.
> 2. If I do a check in via CVS, the headers will be modified,
> So will it be a violation to GPL ?
The answer to your question is: to me, at least, it is not clearly
compliant because it changes the author, which should never be done.
However, these information lines are technical in nature, not part of
the actual source code as such, and it might thus be ok.
But my first answer would actually be a question: why on Earth do
you use CVS for a project that is managed with git? If you used git,
the issue you raise would simply not exist.
> 3. If it is a Violation , please help me with a solution .
Use git. :)
It is free, it is open source, it can (and should) be installed on
every developer's machine to help them manage their own developments,
and on servers to help concentrate said developments, any git copy of
U-Boot can easily be kept in sync with our mainline repository (or any
of the specialized custodian repos)... There really is no reason to use
anything else than git.
> Thanks & Regards,
> Arun
Amicalement,
--
Albert.
next prev parent reply other threads:[~2014-01-20 8:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 7:11 [U-Boot] Uboot_Header_Modification_by_CVS Arun K. Varghese
2014-01-20 8:03 ` Albert ARIBAUD [this message]
2014-01-20 9:57 ` Wolfgang Denk
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=20140120090315.36a7eeee@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