git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] builtin: replace the_repository parameter in is_bare_repository()

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 28, 2026, 22:51 UTC
Message-ID
<xmqqh5kd3lm3.fsf@gitster.g>
In-Reply-To
<CALnO6CCsJGmgmvKyMdX3q1Kr5AnBwYJ=_UiQ9+m7jWe7hv=3Qw@mail.gmail.com>
"D. Ben Knoble" <ben.knoble@gmail.com> writes:
Show 13 quoted lines
>> > Hm. What if a program wants to do « exactly what ‘git switch’ does
>> > » sans shelling out?
>>
>> Instead of cheating, properly factor out reusable part from
>> cmd_checkout() into a set of libified routines, and make both
>> cmd_checkout() and cmd_switch() to call them
>>
>> An approach like that would help "libify" things.  libifying is not
>> just reducing dependence of globals.
>>
>> Calling main() from something else is not a libification.
>
> Sensible. Thanks!
I actually answered a wrong question though ;-) 

The way cmd_switch() and cmd_restore() were introduced by sharing what used to serve cmd_checkout() was serviceable, but ugly. Had we started from separate implementations for 'switch' and 'restore' that were later merged into 'checkout', we would not have ended up with a design centered on a single monolithic choke point like checkout_main().

That is what I meant by "cheating instead of refactoring reusable parts". However, that is not directly relevant to your example.

It is an anti-pattern to call the top-level implementation of 'git foo' in cmd_foo() directly from cmd_bar(), since these cmd_foo() functions are like main() in ordinary programs, performing one-time initialization (such as git_config() calls) and finalization that cannot be repeated. To help our codebase, as well as the use case you imagined in your message, it would help to trim down these non-reusable cmd_foo() implementations by turning them into mere orchestrators that call refactored helper functions. Such a change would put cmd_foo() and a client that wants to reuse 'git switch' functionality on the same footing, allowing more of our code to be used in different contexts. I think that is what people mean by the "libification" effort.

Previous: D. Ben KnobleNext: Junio C Hamano
Message 9 of 47 in “builtin: replace the_repository parameter in is_bare_repository()”
  1. builtin: replace the_repository parameter in is_bare_repository()Hardik Kumar, Aug 27, 2026
  2. Junio C HamanoAug 27, 2026
  3. Junio C HamanoAug 27, 2026
  4. Hardik KumarAug 27, 2026
  5. Junio C HamanoAug 27, 2026
  6. Ben KnobleAug 27, 2026
  7. Junio C HamanoAug 27, 2026
  8. D. Ben KnobleAug 28, 2026
  9. Junio C HamanoAug 28, 2026
  10. 0/8 More sensible checkout/switch/restore code refactoringJunio C Hamano, Aug 28, 2026
  11. 1/8 checkout: pass cb_option explicitly to branch name parsersJunio C Hamano, Aug 28, 2026
  12. 2/8 checkout: validate new branch name in checkout_branch()Junio C Hamano, Aug 28, 2026
  13. 3/8 checkout: validate stage and merge option compatibility in checkout_paths()Junio C Hamano, Aug 28, 2026
  14. 4/8 checkout: extract option validation and pathspec helpersJunio C Hamano, Aug 28, 2026
  15. 5/8 checkout: extract branch setup and tracking helpersJunio C Hamano, Aug 28, 2026
  16. 6/8 checkout: restructure switch, restore, and checkout entrypointsJunio C Hamano, Aug 28, 2026
  17. 7/8 checkout: wrap overly long linesJunio C Hamano, Aug 28, 2026
  18. Junio C HamanoAug 28, 2026
  19. Junio C HamanoAug 29, 2026
  20. 8/8 checkout: move post_checkout_hook() to checkout.cJunio C Hamano, Aug 28, 2026
  21. Junio C HamanoAug 28, 2026
  22. Junio C HamanoAug 29, 2026
  23. 0/8 More sensible checkout/switch/restore code refactoringJunio C Hamano, Aug 30, 2026
  24. 1/8 checkout: pass cb_option explicitly to branch name parsersJunio C Hamano, Aug 30, 2026
  25. Karthik NayakSep 1, 2026
  26. 2/8 checkout: validate new branch name in checkout_branch()Junio C Hamano, Aug 30, 2026
  27. Karthik NayakSep 1, 2026
  28. 3/8 checkout: validate stage and merge option compatibility in checkout_paths()Junio C Hamano, Aug 30, 2026
  29. Karthik NayakSep 1, 2026
  30. Junio C HamanoSep 1, 2026
  31. Karthik NayakSep 2, 2026
  32. Junio C HamanoSep 2, 2026
  33. Karthik NayakSep 3, 2026
  34. 4/8 checkout: extract option validation and pathspec helpersJunio C Hamano, Aug 30, 2026
  35. 5/8 checkout: extract branch setup and tracking helpersJunio C Hamano, Aug 30, 2026
  36. 6/8 checkout: restructure switch, restore, and checkout entrypointsJunio C Hamano, Aug 30, 2026
  37. Karthik NayakSep 1, 2026
  38. Junio C HamanoSep 1, 2026
  39. Karthik NayakSep 2, 2026
  40. 7/8 checkout: wrap overly long linesJunio C Hamano, Aug 30, 2026
  41. 8/8 checkout: move post_checkout_hook() to checkout.cJunio C Hamano, Aug 30, 2026
  42. D. Ben KnobleAug 29, 2026
  43. do not pass "repo" to builtin commmand implementationsJunio C Hamano, Aug 27, 2026
  44. Hardik KumarAug 28, 2026
  45. Junio C HamanoAug 28, 2026
  46. Hardik KumarAug 28, 2026
  47. Hardik KumarAug 27, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.