On Tue, Mar 17, 2009 at 6:50 AM, Menon, Nishanth <n...@ti.com> wrote:
>> -----Original Message-----
>> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
>> ow...@vger.kernel.org] On Behalf Of Felipe Contreras
>> Sent: Tuesday, March 17, 2009 12:06 AM
>> To: linux-omap@vger.kernel.org
>> Cc: Kanigeri, Hari; Hiroshi DOYU; Ameya Palande; Guzman Lugo, Fernando;
>> Felipe Contreras
>> Subject: [PATCH] tidspbridge: remove revision history
>>
>> No need for that with git.
>> diff --git a/drivers/dsp/bridge/gen/_gt_para.c
>> b/drivers/dsp/bridge/gen/_gt_para.c
>> index 181fe41..b363590 100644
>> --- a/drivers/dsp/bridge/gen/_gt_para.c
>> +++ b/drivers/dsp/bridge/gen/_gt_para.c
>> @@ -24,14 +24,6 @@
>>   *      etc. into a fully bound image.  Thus, GT_assert() can be retained
>> in
>>   *      a program for which GT_?trace() has been compiled out.
>>   *
>> - *! Revision History:
>> - *! ================
>> - *! 24-Feb-2003 vp: Code Review Updates.
>> - *! 18-Oct-2002 sb: Ported to Linux platform.
>> - *! 03-Jul-2001 rr: Removed kfuncs.h because of build errors.
>> - *! 07-Dec-1999 ag: Fxn error now causes a WinCE DebugBreak;
>> - *! 30-Aug-1999 ag: Now uses GP_printf for printf and error.
>> - *!
> But we did not have git history 1999-2003. we planning on loosing these 
> contribs?

Only if you want dspbridge to be merged which as time passes it's
becoming more clear that you don't. I'm not a kernel developer, but I
would challenge you to find a diver that has 1000 lines of revision
history in the source code.

Besides, how any of this can be useful?

>> - *! 24-Feb-2003 vp: Code Review Updates.

Ok, what are the updates?

>> - *! 18-Oct-2002 sb: Ported to Linux platform.

So?

>> - *! 03-Jul-2001 rr: Removed kfuncs.h because of build errors.

Nice, but who cares?

>> - *! 07-Dec-1999 ag: Fxn error now causes a WinCE DebugBreak;

Ahh, WinCE history in a Linux driver, very useful.

>> - *! 30-Aug-1999 ag: Now uses GP_printf for printf and error.

Not printk? I assume this is not related to Linux then.


Are we going to find an issue at some point in time that we'll say: oh
crap! if only we had the revision history log we could solve it!

I doubt that, the revision history is useless without the actual
changes. These lines are just introducing noise.

-- 
Felipe Contreras
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to