What's the best way of finding out what's changed and why?
I am trying to determine exactly what code changes have occurred between 2 different releases (including all releases in between). Ideally, I would like to end up with a list of patch and bug references per file. Are changes ever made that don't have a patch or bug reference? I have looked at the ChangeLog and CHANGES files as well as the tracker for bugs and patches but I can't find an obvious way of getting a definitive summary which references all the changes that have occurred. Is this possible? Regards, Adam. -- 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/ ___ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
Re: What's the best way of finding out what's changed and why?
On 9 May 2012 12:12, Lewis Adam-VNQM87 adam.le...@cambiumnetworks.com wrote: I am trying to determine exactly what code changes have occurred between 2 different releases (including all releases in between). That's exactly what ChangeLog is for. It lists all the commit log messages, together with the files affected. CHANGES is designed to extract information about the more important changes, including those affecting tracker entries, but relies on the person making the fix to adopt a particular style of log entry. Inevitably, some of these will be missed. But ChangeLog is completely automatic, so is much more comprehensive. Ideally, I would like to end up with a list of patch and bug references per file. The best way of seeing what changes have been made to a particular code file would be to browse the on-line Git repository. The 'tree' view shows each individual file, including a 'history' link, listing all of the changes that have been made to that particular file. Are changes ever made that don't have a patch or bug reference? Frequently! If you look at ChangeLog, you'll be able to see the entries that reference tracker entries from the Bug or Patches trackers. And these are only a relatively small fraction of the overall code changes. Sometimes we'll be fixing a problem that we've come across, that hasn't been reported via the trackers. Sometimes it will have been reported, but we haven't spotted that entry at the time we fix the problem. Sometimes there's be a tracker entry reported for a problem that has already been fixed. And sometimes we'll just forget to reference the tracker entry that we've been working on. CHANGES is a reasonable indication of which entries have been addressed, and when - but it's not necessarily comprehensive. I have looked at the ChangeLog and CHANGES files as well as the tracker for bugs and patches but I can't find an obvious way of getting a definitive summary which references all the changes that have occurred. Is this possible? ChangeLog and the Git repository history are the best definitive summaries. But they won't necessarily link in with Bug and Patches tracker entries. Dave -- 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/ ___ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
RE: What's the best way of finding out what's changed and why?
Okay, thanks Dave. I didn't look at the Git repository. Dissecting the ChangeLog, a typical couple of entries might be: 2011-09-22 Dave Shield d.t.shi...@liverpool.ac.uk * : commit c55f608f16f160f5e79dc057f8878def462973e1 Author: Dave Shield d.t.shi...@liverpool.ac.uk Date: Thu Sep 22 10:35:24 2011 +0100 2011-09-22 Steve Friedl st...@unixwiz.net * agent/mibgroup/ucd-snmp/disk_hw.c: CHANGES: snmpd: 3409692: Should I be able to ignore everything that doesn't have an explicit file reference or do I need to dig down into lines such as: * : commit c55f608f16f160f5e79dc057f8878def462973e1 -- 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/ ___ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
Re: What's the best way of finding out what's changed and why?
On 9 May 2012 12:48, Lewis Adam-VNQM87 adam.le...@cambiumnetworks.com wrote: Dissecting the ChangeLog, a typical couple of entries might be: 2011-09-22 Dave Shield d.t.shi...@liverpool.ac.uk * : commit c55f608f16f160f5e79dc057f8878def462973e1 Author: Dave Shield d.t.shi...@liverpool.ac.uk Date: Thu Sep 22 10:35:24 2011 +0100 That's actually a truncated version of the full log message: commit 07f61a02a2409096e5c962cd211126396ad09d2b Merge: ee0d3ad bda324b Author: Dave Shield d.t.shi...@liverpool.ac.uk Date: Thu Sep 22 10:39:59 2011 +0100 Merge branch 'V5-5-patches' into V5-6-patches * V5-5-patches: Fix the code for populating the table_tdata cache, and clarify areas needing MIB-specific additions. which tracks back to: 2011-09-22 Steve Friedl st...@unixwiz.net * agent/mibgroup/ucd-snmp/disk_hw.c: CHANGES: snmpd: 3409692: or in full commit ee0d3adb078291b743c9ecb76d20b591b7b15972 Author: Steve Friedl st...@unixwiz.net Date: Thu Sep 22 09:58:39 2011 +0100 CHANGES: snmpd: 3409692: Calculate disk percentage usage via floating-point arithmetic to avoid integer overflow errors. (Code based on the submitted patch, rather than applied verbatim) We switched from SVN to Git in June last year, and I have a feeling that it took a while to get the most sensible form of log messages (in a form that the ChangeLog generation script could do something with). It may be that this was one of the less-informative entries! I doubt it's safe to ignore any ChangeLog entries, without having a clearer idea of what they affected. Dave -- 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/ ___ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
Re: What's the best way of finding out what's changed and why?
On Wed, 9 May 2012 06:12:18 -0500 Lewis wrote: LAV I am trying to determine exactly what code changes have occurred between LAV 2 different releases (including all releases in between). if you are in git, you can run git [--reverse] log V5-5-patches..V5-6-patches -- 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/ ___ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
