Re: [PATCH 00/20] Fix typos
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Sep 19, 2024, 20:42 UTC
- Message-ID
- <xmqq34lv74us.fsf@gitster.g>
- In-Reply-To
- <ab9213d5-fb1b-482e-854b-4f5d4e82821a@app.fastmail.com>
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:
Show 5 quoted lines
> All of these look correct. > > Maybe all of the commits could be combined into one commit with the > message “treewide: fix typos”. But that wasn’t asked for last time.[1] > So I dunno.
It depends. When done carefully to make sure that nothing textually conflicts with any topics in flight, a single "treewide" patch is slightly nicer. If nothing conflicts with nothing else, either format is fine. If something have nasty conflicts (e.g., a refactor moved the comment with typos far from the original location or even to a different file), individual patch form is easier to discard the ones that need to wait.
I do not know which case this 20-patch collection falls into.
Thanks.