# git gc
Expanding reachable commits in commit graph: 81988
Expanding reachable commits in commit graph: 171609
Expanding reachable commits in commit graph: 262224
Expanding reachable commits in commit graph: 354391
Expanding reachable commits in commit graph: 451235
Expanding reachable commits in commit graph: 536569
Expanding reachable commits in commit graph: 636691
Expanding reachable commits in commit graph: 738951
Expanding reachable commits in commit graph: 843793
Expanding reachable commits in commit graph: 951875
Expanding reachable commits in commit graph: 1054601
Expanding reachable commits in commit graph: 1145683
Expanding reachable commits in commit graph: 1235470, done.
Writing out commit graph in 4 passes:  60% (2996050/4941880)
Writing out commit graph in 4 passes:  61% (3014547/4941880)
Writing out commit graph in 4 passes:  62% (3063966/4941880)
Writing out commit graph in 4 passes:  63% (3113385/4941880)
Writing out commit graph in 4 passes:  64% (3162804/4941880)
Writing out commit graph in 4 passes:  65% (3212222/4941880)
Writing out commit graph in 4 passes:  66% (3261641/4941880)
Writing out commit graph in 4 passes:  67% (3311060/4941880)
Writing out commit graph in 4 passes:  68% (3360479/4941880)
Writing out commit graph in 4 passes:  69% (3409898/4941880)
Writing out commit graph in 4 passes:  70% (3459316/4941880)
Writing out commit graph in 4 passes:  71% (3508735/4941880)
Writing out commit graph in 4 passes:  72% (3558154/4941880)
Writing out commit graph in 4 passes:  73% (3607573/4941880)
Writing out commit graph in 4 passes:  74% (3656992/4941880)
Writing out commit graph in 4 passes:  74% (3658972/4941880)
Writing out commit graph in 4 passes:  75% (3706410/4941880)
Writing out commit graph in 4 passes:  76% (3755829/4941880)
Writing out commit graph in 4 passes:  77% (3805248/4941880)
Writing out commit graph in 4 passes:  78% (3854667/4941880)
Writing out commit graph in 4 passes:  79% (3904086/4941880)
Writing out commit graph in 4 passes:  80% (3953504/4941880)
Writing out commit graph in 4 passes:  81% (4002923/4941880)
Writing out commit graph in 4 passes:  82% (4052342/4941880)
Writing out commit graph in 4 passes:  83% (4101761/4941880)
Writing out commit graph in 4 passes:  84% (4151180/4941880)
Writing out commit graph in 4 passes:  85% (4200598/4941880)
Writing out commit graph in 4 passes:  86% (4250017/4941880)
Writing out commit graph in 4 passes:  87% (4299436/4941880)
Writing out commit graph in 4 passes:  88% (4348855/4941880)
Writing out commit graph in 4 passes:  89% (4398274/4941880)
Writing out commit graph in 4 passes:  90% (4447692/4941880)
Writing out commit graph in 4 passes:  91% (4497111/4941880)
Writing out commit graph in 4 passes:  92% (4546530/4941880)
Writing out commit graph in 4 passes:  93% (4595949/4941880)
Writing out commit graph in 4 passes:  94% (4645368/4941880)
Writing out commit graph in 4 passes:  95% (4694786/4941880)
Writing out commit graph in 4 passes:  96% (4744205/4941880)
Writing out commit graph in 4 passes:  97% (4793624/4941880)
Writing out commit graph in 4 passes:  98% (4843043/4941880)
Writing out commit graph in 4 passes:  99% (4892462/4941880)
Writing out commit graph in 4 passes: 100% (4941880/4941880)
Writing out commit graph in 4 passes: 100% (4941880/4941880), done.
# git rev-parse -q --verify 2639772a11c860628c5f7007842eca52a1c34d78^{commit}
2639772a11c860628c5f7007842eca52a1c34d78
already have revision, skipping fetch
# git checkout -q -f -B kisskb 2639772a11c860628c5f7007842eca52a1c34d78
# git clean -qxdf
# < git log -1
# commit 2639772a11c860628c5f7007842eca52a1c34d78
# Author: Alvin Šipraga <alsi@bang-olufsen.dk>
# Date:   Tue Dec 19 02:25:15 2023 +0100
# 
#     get_maintainer: remove stray punctuation when cleaning file emails
#     
#     When parsing emails from .yaml files in particular, stray punctuation
#     such as a leading '-' can end up in the name.  For example, consider a
#     common YAML section such as:
#     
#       maintainers:
#         - devicetree@vger.kernel.org
#     
#     This would previously be processed by get_maintainer.pl as:
#     
#       - <devicetree@vger.kernel.org>
#     
#     Make the logic in clean_file_emails more robust by deleting any
#     sub-names which consist of common single punctuation marks before
#     proceeding to the best-effort name extraction logic.  The output is then
#     correct:
#     
#       devicetree@vger.kernel.org
#     
#     Some additional comments are added to the function to make things
#     clearer to future readers.
#     
#     Link: https://lore.kernel.org/all/0173e76a36b3a9b4e7f324dd3a36fd4a9757f302.camel@perches.com/
#     Suggested-by: Joe Perches <joe@perches.com>
#     Signed-off-by: Alvin Šipraga <alsi@bang-olufsen.dk>
#     Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
# < /opt/cross/kisskb/x86-64--glibc--bleeding-edge-2022.08-1/bin/x86_64-linux-gcc --version
# < /opt/cross/kisskb/x86-64--glibc--bleeding-edge-2022.08-1/bin/x86_64-linux-ld --version
# < git log --format=%s --max-count=1 2639772a11c860628c5f7007842eca52a1c34d78
# make -s -j 40 ARCH=um O=/kisskb/build/linus_defconfig_um-x86_64-gcc12 CROSS_COMPILE=/opt/cross/kisskb/x86-64--glibc--bleeding-edge-2022.08-1/bin/x86_64-linux- SUBARCH=x86_64 defconfig
# < make -s -j 40 ARCH=um O=/kisskb/build/linus_defconfig_um-x86_64-gcc12 CROSS_COMPILE=/opt/cross/kisskb/x86-64--glibc--bleeding-edge-2022.08-1/bin/x86_64-linux- SUBARCH=x86_64 help
# make -s -j 40 ARCH=um O=/kisskb/build/linus_defconfig_um-x86_64-gcc12 CROSS_COMPILE=/opt/cross/kisskb/x86-64--glibc--bleeding-edge-2022.08-1/bin/x86_64-linux- SUBARCH=x86_64 olddefconfig
# make -s -j 40 ARCH=um O=/kisskb/build/linus_defconfig_um-x86_64-gcc12 CROSS_COMPILE=/opt/cross/kisskb/x86-64--glibc--bleeding-edge-2022.08-1/bin/x86_64-linux- SUBARCH=x86_64 
  LINK linux
Completed OK
# rm -rf /kisskb/build/linus_defconfig_um-x86_64-gcc12
# Build took: 0:04:41.839948