From: Patrick Talbert on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1209#note_640992132 For very simple changes such as toggling a config option I have sometimes edited the file with gitlab's UI which creates a new commit. But then we squash the commits upon merge. In the instances where I checkout the branch, edit, and push the change, I typically amend the commit message with a V2 line showing _what_ I toggled, but not _why_. In many cases I do not have a "why" beyond some RH SME suggesting they would like it changed and we'll have the MR history and mailing list history if we ever want to go back to see that... _______________________________________________ kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kernel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
