summaryrefslogtreecommitdiff
path: root/reviews/emacs/hype.org
diff options
context:
space:
mode:
authorKévin Le Gouguec <kevin.legouguec@gmail.com>2022-10-29 13:27:03 +0200
committerKévin Le Gouguec <kevin.legouguec@gmail.com>2022-10-29 13:27:03 +0200
commitecf10606d4fa423571f6802a30dddf57a10eab1c (patch)
tree584f1745b00c832415e4ce800868d36e801993f5 /reviews/emacs/hype.org
parent1fd86635555042119cf0445913d521b366f89aa3 (diff)
downloadmemory-leaks-ecf10606d4fa423571f6802a30dddf57a10eab1c.tar.xz
Mark ada-mode itch as scratched
The way upstream handled that one was somewhat confusing. The timeline I remember: 1. November 2021: bug opened. 2. May 2022: bug closed, with no acknowledgment of patches whatsoever: > Date: Sat, 28 May 2022 04:15:57 -0700 > Closed by ada-mode version 7.2.1, uniquify-files version 1.0.4. _AFAIR_ (and this is where I doubt my own sanity), those new versions were never pushed anywhere public? The commit dates that eventually made it to the GNU ELPA repo show that the patches were applied on May 28, so you'd think I should have been able to see them, but I distinctly remember seeing the bug-closed notification and expectantly looking at GNU ELPA (via list-packages, the website, and finally fetching from the git repo) and seeing *nothing*. 3. July 2022: the new package versions mentioned in the bug-closed notification are finally published on GNU ELPA; elpa.git is updated; I check the log and don't see my patches; I check the sources and do end up finding my changes. OT1H I certainly won't presume to tell upstream how to handle user contributions; OTOH the combination of (1) the curt closing message that neither ACK'ed nor NACK'ed the patches (2) the months-long radio silence between closing and releasing (3) the loss of attribution, all make for a rather austere contribution process.
Diffstat (limited to 'reviews/emacs/hype.org')
0 files changed, 0 insertions, 0 deletions