PuTTY hosts its code at svn://svn.tartarus.org/sgt/putty.

You can learn more at the project's web page.

Launchpad imports the master branch and you can create branches from it.

You can browse the source code for the development focus branch or get a copy of the branch using the command:
bzr branch lp:putty

PuTTY has 2 active branches owned by 1 team. There were 8 commits by 2 people in the last month.

Bazaar branches

Name Status Last Modified Last Commit
lp:putty
Series: trunk
1 Development 2014-10-21 11:33:33 UTC 2014-10-21
3757. Cross-reference the description of wi...

Author: jacob
Revision Date: 2014-10-21 11:33:33 UTC

Cross-reference the description of winadj@putty.projects.tartarus.org
to its bug-compatibility mode.

lp:~vcs-imports/putty/master 1 Development 2019-08-19 19:38:15 UTC 2019-08-19
5533. Unix Plink: stop zeroing out the term...

Author: Simon Tatham
Revision Date: 2019-08-19 19:38:15 UTC

Unix Plink: stop zeroing out the terminal size in pty-req.

I noticed today that when you use Unix Plink interactively, to run a
tty session on a remote host starting from a local tty, it doesn't
copy the local terminal size into the "pty-req" channel request.

It looks as if this is a bug introduced in 2ca0070f8, when I broke up
ssh.c. Before that, the monolithic Ssh init procedure set
ssh->term_width and ssh->term_height from the Conf you passed in.
Afterwards, variables of the same name existed in both ssh.c *and*
ssh2connection.c (the former so that it can buffer window-size changes
before a connection layer yet exists to pass them on to), but somehow,
*neither* source file remembered to initialise them from the Conf.

Fixed by reinstating the initialisation in ssh.c. (For the same reason
as above: you want the values in Conf to be overwritten if the window
size changes between ssh_init and ssh2_connection_new.)

12 of 2 results
You can't create new branches for PuTTY.