1For an overview of what's changed in this release, see pod/perldelta.pod. 2 3For the details of changes in previous releases, see the individual 4perlNNNdelta.pod files. For example, pod/perl588delta.pod describes the 5changes between versions 5.8.7 and 5.8.8. 6 7For a list of contributors to perl, see AUTHORS. 8 9If you need a detailed commit history (i.e. descriptions of each 10individual commit), you can view the git version control history online 11at http://perl5.git.perl.org/perl.git (follow the 'shortlog' link beside 12the relevant tag). Or, you can download a copy of the git repository and 13then run a command like 14 15 git log --name-status perl-5.10.0..perl-5.11.0 16 17to view all the changes between 5.10.0 and 5.11.0. 18 19Specifically, the changes for this release, (i.e. between 5.10.0 and 205.10.1), is shown with with following command. Note that the range 21specification is slightly unusual for this release due to some kinks while 22migrating to git. 23 24 git log --name-status perl-5.10.0^..perl-5.10.1 ^f7c6915850 25 26See pod/perlrepository.pod for more details on using git and accessing the 27commit history. 28 29In perl releases prior to 2009, the source tarball included a collection 30of Changes files that listed the individual commits that had gone into 31each release. Since these files had become very large, and since the 32same information is now freely available online, it was decided to remove 33them from subsequent releases. 34 35If you need access to these removed files, then they can be be found most 36recently in the 5.8.9 and 5.10.0 tarballs, at 37 38 http://www.cpan.org/src/perl-5.8.9.tar.gz 39 http://www.cpan.org/src/perl-5.10.0.tar.gz 40 41The contents of the files in question can mostly be regenerated using git 42commands. The following table shows the equivalents. Note that the files 43prior to Changes5.005 were not simple lists of commits, so can't be 44recreated just by running the git command. As it happens, even the latter 45ones are not exact equivalents. This is due to a combination of errors in 46the original Changes files, and "impedance mismatches" when the previous 47version control data was imported into git in December 2008. 48 49For example, the Changes5.005 file includes 206 spurious entries from the 50maint5.004 Perforce branch. 51 52Running the following command with the range argument shown in the table 53will produce *approximately* the same list of changes in the specified 54file shown from the listed tarball. 55 56 git log --name-status <range> 57 58 file tarball <range> argument to 'git log' 59 ------------ ------ -------------------------------- 60 Changes5.000 Either N/A 61 Changes5.001 Either perl-5.000..perl-5.001 62 Changes5.002 Either perl-5.001..perl-5.002 63 Changes5.003 Either perl-5.002..perl-5.003 64 Changes5.004 Either perl-5.003..perl-5.004 65 Changes5.005 Either perl-5.004..perl-5.005_03 66 Changes5.6 Either perl-5.005_03..perl-5.6.0 67 Changes5.8 Either perl-5.6.0..perl-5.8.0 68 Changes5.8.1 5.8.9 perl-5.8.0..perl-5.8.1 ^1ede746b 69 Changes5.8.2 5.8.9 perl-5.8.1..perl-5.8.2 70 Changes5.8.3 5.8.9 perl-5.8.2..perl-5.8.3 71 Changes5.8.4 5.8.9 perl-5.8.3..perl-5.8.4 72 Changes5.8.5 5.8.9 perl-5.8.4..perl-5.8.5 ^3a81978b 73 Changes5.8.6 5.8.9 perl-5.8.5..perl-5.8.6 ^498d59dd 74 Changes5.8.7 5.8.9 perl-5.8.6..perl-5.8.7 75 Changes5.8.8 5.8.9 perl-5.8.7..perl-5.8.8 76 Changes 5.8.9 perl-5.8.8..perl-5.8.9 77 Changes 5.10.0 perl-5.8.0..perl-5.10.0 78