Re: What's the best way of finding out what's changed and why?

2012-05-09 Thread Robert Story
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

Re: What's the best way of finding out what's changed and why?

2012-05-09 Thread Dave Shield
On 9 May 2012 12:48, Lewis Adam-VNQM87 wrote: > Dissecting the ChangeLog, a typical couple of entries might be: > > 2011-09-22  Dave Shield > >   * : commit c55f608f16f160f5e79dc057f8878def462973e1 Author: Dave >  Shield Date:   Thu Sep 22 10:35:24 2011 >  +0100 That's actually a truncated vers

RE: What's the best way of finding out what's changed and why?

2012-05-09 Thread Lewis Adam-VNQM87
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 * : commit c55f608f16f160f5e79dc057f8878def462973e1 Author: Dave Shield Date: Thu Sep 22 10:35:24 2011 +0100 2011-09-22 Steve Friedl *

Re: What's the best way of finding out what's changed and why?

2012-05-09 Thread Dave Shield
On 9 May 2012 12:12, Lewis Adam-VNQM87 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. CHANG

What's the best way of finding out what's changed and why?

2012-05-09 Thread Lewis Adam-VNQM87
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 C