Port #33631 to dev16.0 (Low priority for code wrapping refactorings)

[mavasani]

Code wrapping refactorings should be lower pri than other refactorings

Ports #33631 to dev16.0 branch

[CyrusNajmabadi]

@mavasani was this just a cherry-pick? if so, if you do cherry-pick -x it will keep track of the original commit hash.

[mavasani]

@CyrusNajmabadi I am trying still having a hard time to retain the same commit hash. I attempted git cherry-pick -x 8d53065 -m 1 but that still creates a new commit hash.

[CyrusNajmabadi]

@CyrusNajmabadi I am trying still having a hard time to retain the same commit hash. I attempted git cherry-pick -x 8d53065 -m 1 but that still creates a new commit hash.

Sorry, i wasn't clear. You'll def get a new commit hash. It's just that by doing -x this new commit will properly point to the cherrypicked commit.

[CyrusNajmabadi]

-x

When recording the commit, append a line that says "(cherry picked from commit …​)" to the original commit message in order to indicate which commit this change was cherry-picked from. This is done only for cherry picks without conflicts. Do not use this option if you are cherry-picking from your private branch because the information is useless to the recipient. If on the other hand you are cherry-picking between two publicly visible branches (e.g. backporting a fix to a maintenance branch for an older release from a development branch), adding this information can be useful.

It's a minor thing. But it helps me know that thsi was just a cherry.

[mavasani]

@CyrusNajmabadi Thanks, just force pushed c9183bd

[jinujoseph]

Once merged will be available in 16.RC.2

[CyrusNajmabadi]

Thanks. if this is just a CP, with no changes. the 👍 from me

[CyrusNajmabadi]

Thanks!