Am 04.09.2012 um 23:46 schrieb Kent A. Reed: > > > Also, Michael, I think even experimental code in master should have at > least a minimal comment section identifying programmer, date, status. > Nudge, nudge, wink, wink, know what I mean?
my moderate ego doesnt allow for such blatant scent marks ;) well, you're right. for author forensics, 'git blame' is very useful, try: git blame hal/simdrivers/ppioctl.c - Michael ps: right now the uparport.c,h files are temporary copies of hal_parport.c,h . Once this shakes out, I'll merge the changes into hal_parport.c,h which will then have the proper git history; for now the uparport.? git history is useless. > > Regards, > Kent > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Emc-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-developers ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
