- From: Cosmin Truta <ctruta@gmail.com>
- Date: Tue, 18 Feb 2025 19:29:05 +0200
- To: Chris Lilley <chris@w3.org>
- Cc: public-png@w3.org, Greg Roelofs <newt@pobox.com>
- Message-ID: <CAAoVtZwbiP7u6xTmz3wx8y7Srp4nS6tUFHETn3AE3P=9nUTOBw@mail.gmail.com>
On Feb 14, 2025 at 6:13 PM Chris Lilley wrote: >> https://github.com/ctruta/pngcheck > I used VSCode. History looks great. Alrighty then (but in the way Jim Carrey would say it). > Because of the repo transfer, we did lose the edit where the readme was changed from "unofficial" to "development" but that it trivial to do again. I made that edit after my first rebuild of the history, but then I changed my mind and I ostensibly omitted it the second time around. I mean, you should do the honours of making it official, Sir! 😄 > There is also a recent PR which hasn't been approved, so is not in the history. I assume we won't lose that? Or the existing (open and closed) issues? > https://github.com/pnggroup/pngcheck/pull/19 If we lost it, it would have been my fault, or GitHub's fault. Or both. But we didn't, so, we're good. Better yet: the graphical rendition of the Git history looks even better now, because your commit just became the most recent before the merge, which makes at least some of the Git visualisation tools (like "git log --graph" and "gitk") to heuristically display your branch entirely ahead of my branch -- which is how the history truly is 🤓 I will send the official announcement on png-implement later today. (Wooo-hooo I'm excited!) Sincerely, Cosmin
Received on Tuesday, 18 February 2025 17:29:20 UTC