Conversation

Notices

1. Embed this notice
   Account: Computers (pro@mu.zaitcev.nu)'s status on Thursday, 04-Sep-2025 06:57:42 JST Account: Computers

   in reply to

   • penguin42
   • Marcin Juszkiewicz 🙃
   @penguin42 @hrw I hate submodules very much too. However, their implementation has become far less buggy in the last couple of years. It used to be extremely easy to break your repository completely with them. But in 2025 you can live with them with little trouble for months, maybe even years. BTW, it's "git submodule update". Don't do -f. The main remaining reason for my hate is how easy to is to forget to update them. And a less important reason is that branches are prevalent in modern git workflows (instead of cloning), and they conflict with submodules.
   • Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     penguin42 (penguin42@mastodon.org.uk)'s status on Thursday, 04-Sep-2025 06:57:44 JST penguin42

     in reply to

     • Marcin Juszkiewicz 🙃

     @hrw Blech, I hate them!

   • Embed this notice
     Marcin Juszkiewicz 🙃 (hrw@society.oftrolls.com)'s status on Thursday, 04-Sep-2025 06:57:47 JST Marcin Juszkiewicz 🙃

     Git submodules are handy way to share files between projects.

     At same time they are PITA when it comes to updating.

     `git submodule update`?
     `git submodule update -f`?
     `git submodule sync`?

     I am starting to consider dropping submodule in favour of manual cherry-picking update between repos.