This repository has been archived by the owner on Apr 19, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 94
Other forks of PuTTY
FauxFaux edited this page Jan 14, 2012
·
20 revisions
I'd like to merge all the compatible code from as many forks as possible.
I am currently aware of:
- http://code.google.com/p/portaputty/ , abandoned since 2007, PuTTY 0.60.
- https://github.com/FauxFaux/PuTTYTray/tree/portaputty-steveman-0.62 - "steveman"'s rebase of this upon PuTTY 0.62.
- Most of the PuTTYTray patches, but with only file store support.
- This does not merge; they drop support for the registry and just go with files, so winstore.c is a mess. Everything else is similar, I believe; haven't checked.
- http://jakub.kotrla.net/putty/ , active 2011, PuTTY 0.61
- Just drops the registry code and replace it with a new winstore.c, again, no merging.
- https://bitbucket.org/daybreaker/iputty/ , active 2012, PuTTY 0.62.
- Some of the smaller PuTTYTray patches, plus IME support, Korean localisation, extra hotkeys, and other cool stuff.
- Large diff, doesn't quite align with my PuTTYTray tree as I've reordered some lines doing the commit splitting (argh), so hard to merge. Would at least like to steal the IME support, or maybe get "daybreaker" to move to git(?!).
- http://portableapps.com/apps/internet/putty_portable , active 2012, PuTTY 0.62.
- No code changes. Portability is implemented through a launcher which dumps/restores the registry to a file. Could implement similar functionality? Not really any point, as it's horrible.
- https://dev.daybreaker.info/dputty , SVN repo down, guessing abandoned for iPuTTY (same author).
- ??? , even older version of dPuTTY
- http://hp.vector.co.jp/authors/VA024651/PuTTYkj.html , active 2011, PuTTY 0.62; no source that I can see.
- Support for EUC and ISO-2022, and other East-Asian encodings.
- http://www.kelley.ca/amd64/ , abandoned since 2007, PuTTY 0.59.
- Can't find source; diff link 404s.
- Guessing patches went into core, or anything they did was fixed. x64 build currently works fine, as far as I'm aware.