https://bugzilla.kernel.org/show_bug.cgi?id=100221
--- Comment #46 from Kumar <[email protected]> --- (In reply to Aaron Lu from comment #45) > (In reply to Kumar from comment #44) > > Just 1 more question : > > > > 1) How can I check all the commite between v3.18 & v3.19 ? > > Use git bisect, it's designed for this purpose. > > > > > 2) Suppose I get a commit ID abc, then should I be doing the following : > > If you get the commit ID abc by using git bisect, then -> > > > > > git reset --hard abc > > <- > no, you shouldn't reset here, you just build the kernel, no need to change > kernel config either, just build and according to test result, tell git > bisect the result with "git bisect good" or "git bisect bad". > > > make menuconfig > > make -j 4 ; make modules_install install > > > > Please do correct me , if I'm wrong. > > Like I said above, if you are in the process of bisecting, no need to do > "git reset", the bisect will automatically check out the code according to a > specified commit abc. > > If you are just testing out a specified commit without using bisect, then > yes, you can do the steps as you have written. But since there are a huge > lot of commits between v3.18 and v3.19, you really shouldn't test commit one > by one, instead, please use bisect. > > > > > Thanks & Regards > > Kumar Abhishek That was really nice and helpful of you. Thanks a lot. Will share the results within a day or 2. Regards Kumar Abhishek -- You are receiving this mail because: You are watching the assignee of the bug. ------------------------------------------------------------------------------ _______________________________________________ acpi-bugzilla mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
