Hello Richard, Thank you for your help. I want to be sure that I'll not miss some important commits so I'll check them all.
Best regards, Vitalii Koshura 2017-03-29 10:56 GMT+03:00 Richard Haselgrove <[email protected]> : > Using TortoiseGit on a clone, I found that viewing the log from the client > and clientgui folders only - effectively filtering to select commits which > touched files in those folders only - generated a shortlist which might be > helpful. > > > On Wednesday, 29 March 2017, 8:40, Vitalii Koshura < > [email protected]> wrote: > > > Hello Oliver, > > Thank you for advice. > From my POV the the most hard part of this is to select important commits > only. > > Best regards, > Vitalii Koshura > > 2017-03-29 9:36 GMT+03:00 Oliver Bock <[email protected]>: > > > Hi Vitalii, > > > > On 28/03/2017 9:34 , Vitalii Koshura wrote: > > > I can do the hard job and prepare the list of commits for 7.7 release > and > > > also prepare the list of fixes with issue numbers. > > > > That doesn't need to be hard. Just use git (log) and generate the > > changelog. All you need to know to do that are the start and end points > > (SHA1s) of the range of commits - but you have to know those as well to > > it manually. > > > > Best, > > Oliver > > > > > _______________________________________________ > boinc_dev mailing list > [email protected] > https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > To unsubscribe, visit the above URL and > (near bottom of page) enter your email address. > > > _______________________________________________ boinc_dev mailing list [email protected] https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
