Conversation

Notices

1. Embed this notice
   silverwizard (silverwizard@convenient.email)'s status on Thursday, 01-Dec-2022 05:25:06 JST silverwizard
   The biggest mistake in git was commit messages
   • Embed this notice
     silverwizard (silverwizard@convenient.email)'s status on Thursday, 01-Dec-2022 05:52:04 JST silverwizard

     in reply to

     • Dave
     @dj3vande Yeah - but commit messages are the thing that basically breaks all the flow of git. All the things that makes git *good* and ruined by the existence of commit messages
   • Embed this notice
     Dave (dj3vande@convenient.email)'s status on Thursday, 01-Dec-2022 05:52:06 JST Dave

     in reply to
     @silverwizard That's a pretty strong statement about everything else in git.
   • Embed this notice
     silverwizard (silverwizard@convenient.email)'s status on Thursday, 01-Dec-2022 06:39:07 JST silverwizard

     in reply to

     • Dave
     @dj3vande Yeah, but the problem is that people build workflows around commit messages. So you get a git log containing "Just committing this for the evening" and "FUck, I think this was right? Lemme send it to you" but then people want to take those events and process them. We need to have *merge* messages
   • Embed this notice
     Dave (dj3vande@convenient.email)'s status on Thursday, 01-Dec-2022 06:39:08 JST Dave

     in reply to
     @silverwizard I mean, that's also pretty easy to fix:
     
     #!/bin/sh
     # git-mcommit - commit with a default message
     exec git commit -m "$(git diff --cached --stat)" "$*"