Okay. Thanks a lot for the below information. I have a query here so does that mean each single commit id corresponds to every single bug fix?
Regards, Guru On Mon, Aug 03, 2015 at 10:21 pm, Joe Stringer <[email protected]<mailto:[email protected]>> wrote: Github also allows you to browse commits by tag, eg: https://github.com/openvswitch/ovs/commits/v2.3.2 On 3 August 2015 at 09:38, Justin Pettit <[email protected]> wrote: > The best way to see what was fixed is to look at the commit history. Here's > the github history for branch-2.3: > > https://github.com/openvswitch/ovs/commits/branch-2.3 > > We tag every release, and you can see the commit id on this page: > > https://github.com/openvswitch/ovs/tags > > If you use a tool like gitk, you can see both commits and tags together. I'm > not sure if github provides such a facility. If you spend a few minutes with > the git command line tool, I'm sure you can find a way to list all the > commits between two tags. > > --Justin > > >> On Aug 2, 2015, at 9:40 PM, Karnataki, Gururaj <[email protected]> >> wrote: >> >> Team, >> >> Can anyone please guide me with the list of bug fixes for OVS 2.3.2. The >> official release info does not seem to have all this. Eagerly awaiting for >> all related responses in this regards. >> >> >> >> Thank You, >> Gururaj Karnataki >> Product Engineer, Systems Integrator >> >> NTT Communications >> powered by Virtela >> >> Desk +1-720-475-9243 >> Cell +91-75063-88977 >> www.ntt.com<http://www.ntt.com/> >> www.virtela.net<http://www.virtela.net/> >> >> >> _______________________________________________ >> dev mailing list >> [email protected] >> http://openvswitch.org/mailman/listinfo/dev > > _______________________________________________ > dev mailing list > [email protected] > http://openvswitch.org/mailman/listinfo/dev _______________________________________________ dev mailing list [email protected] http://openvswitch.org/mailman/listinfo/dev
