Comment on The Jujutsu version control systemparentComments−adastra221yYou can edit your commit message ahead of time in git too.−crabmusket1yWhat's your workflow like to do this?−Superfud1yInitial empty commit with just a message you can create with "git commit --allow-empty -m'Early commit message"Then when you have the changes lined up you --amend that same commit.−xorcist1yThere's nothing to it, it's just "git commit".You then add your changes and "git commit --amend".(These could be aliases. Mine are "ci" and "ca" respectively.)−adastra221yYou can do that. But I mean there is literally a spot in the .git directory for the work-in-progress commit message. When you later do git commit -a or whatever, it pulls up the message.−stavros1yIs there any way you can be specific enough for people to reproduce this?−adastra221yI don’t do it, because I don’t find it valuable. I’m kinda confused at why patent poster wants to do this. Just pointing out that git supports it too.
Comments
You can edit your commit message ahead of time in git too.
What's your workflow like to do this?
Initial empty commit with just a message you can create with "git commit --allow-empty -m'Early commit message"
Then when you have the changes lined up you --amend that same commit.
There's nothing to it, it's just "git commit".
You then add your changes and "git commit --amend".
(These could be aliases. Mine are "ci" and "ca" respectively.)
You can do that. But I mean there is literally a spot in the .git directory for the work-in-progress commit message. When you later do git commit -a or whatever, it pulls up the message.
Is there any way you can be specific enough for people to reproduce this?
I don’t do it, because I don’t find it valuable. I’m kinda confused at why patent poster wants to do this. Just pointing out that git supports it too.