- From: Cosmin Truta <ctruta@gmail.com>
- Date: Fri, 14 Feb 2025 01:29:54 +0200
- To: public-png@w3.org
- Cc: Greg Roelofs <newt@pobox.com>, Chris Lilley <chris@w3.org>
- Message-ID: <CAAoVtZxP+FfF_naAFnvQV5-3bWvbmd9keM4agsWTSE5Opq0LLA@mail.gmail.com>
Greg, Chris, and anybody else who's interested in pngcheck, Could you please review my pngcheck history reconstruction, preferably with a tool that does history visualization, from "git log --graph" to VSCode and everything in between. (BTW, I use "tig" from the terminal, which is lightning fast and freaking awesome.) https://github.com/ctruta/pngcheck Greg: I included (I think) all source files that you gave me, with the exception of "pngcheck-1.81-19950904-grr.c", which turned out to be an evolutionary dead end. If you need time to go over those commits and make sure that the history that I reconstructed from your files is matching the one that you remember (however vaguely) you should know that I'm not in a hurry. I'd rather be sure that you catch my error(s) before I move it over to the official repo at github.com/pnggroup. Chris, Greg: Unlike the last time, when I rebased Chris' history over Greg's history, this time around I kept Chris' history intact by doing an octopus merge, which some people like, but others don't. An advantage: it's a simple business-as-usual merge. A disadvantage: those who habitually use "git log" and especially "git log --patch" from the terminal will probably have a harder time than those who use visual tools, at least for now. So, if you don't like that, for any reason, and you'd rather prefer that I do what I did last time instead, i.e. rebase Chris' history of recent modifications over Greg's original history, please tell me, and I'll redo that. After you confirm that everything looks ok to you, we'll promote this new tree to its canonical home at github.com/pnggroup/pngcheck. Sincerely, Cosmin
Received on Thursday, 13 February 2025 23:30:10 UTC