On Wed, Mar 18, 2009 at 8:36 AM, Menon, Nishanth <nm@xxxxxx> wrote: >> -----Original Message----- >> From: Trilok Soni [mailto:soni.trilok@xxxxxxxxx] >> Sent: Wednesday, March 18, 2009 8:26 AM >> To: David Brownell >> Cc: Felipe Contreras; Menon, Nishanth; Kanigeri, Hari; linux- >> omap@xxxxxxxxxxxxxxx; Hiroshi DOYU; Ameya Palande; Guzman Lugo, Fernando >> Subject: Re: [PATCH] tidspbridge: remove revision history >> >> >> >> >> I have no idea why I'm in that list. >> >> >> > >> > These short names looks like are given to TI internal developers not >> > the open-source contributors to this code. So, "ag" can mean "Amit >> > Agrawal" or "Andy Grover" or anything else... >> > >> > Better to remove these short names from the revision history, it >> > doesn't have any meaning. >> > >> >> Nishanth probably can put some points here. >> > Cards on table: I have never been involved personally on DSPBridge :(.. > It is just this: as a developer we all contribute to something so that our legacy remains in some form.. Agreed various other motivations exist ;).. > > But personally, it feels good to see a tiny contribution being part of something else and being acknowledged for it.. do we as a community say: > a) Lets kick all those oldies out.. They were yesteryear material, we can afford to forget them now. > OR do we say > b) Lets find who those guys are and ask them how they want to acknowledged here.. > > I mean, we all hate dirty code.. and I personally agree to Felipe's point that much of the old time revision history is eating bytespace and eyespace :(.. At the same time, I guess we still retain the old courtesy b/w one code hack to another :D.. I thought b) was kind of agreed. In any case, after cleaning up the dsp-bridge I don't think many files will stay alive, many already have been removed (e.g. [1]), but let's see how it goes. [1] http://github.com/felipec/linux-omap/commit/8ab33fe0a83058d2f9be906c89842ff4486ce68b -- Felipe Contreras -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
