At 18:17 -0800 22 Feb 2022, "Kevin J. McCarthy" <ke...@8t8.us> wrote:
On Tue, Feb 22, 2022 at 04:27:25PM -0800, Kevin J. McCarthy wrote:On Tue, Feb 22, 2022 at 07:07:42PM -0500, Aaron Schrab wrote:955d281f6 (Add missing period in a comment., 2021-04-08) [...]That was a merge request from someone on gitlab. It fixes a typo in a code comment, so (IMO) doesn't need to go into a stable release.Sorry I missed the point of confusion here.The "AuthorDate:" for the commit is 2021-04-08. I presume it sat in their own branch for the last year and they put it into a merge request after the 2.2.0 release.However the "CommitDate:" is 2022-02-13.
Ahh, yes. I hadn't considered that such a simple change would be held for that long. If I'd seen that commit date I wouldn't have asked about that.
For larger, more complex changes it can make a bit more sense. The one change that I apply on top of master is nearing 5 years from the commit date without being submitted, since I keep putting off writing decent documentation for it.
signature.asc
Description: PGP signature
