Hi, I think that perhaps there is a misunderstanding - the perl script didn't do any of these things for me.
Running this in declarative gives me: ~/dev/qtsdk/packaging-tools/create_changelog.pl $PWD 5.5.1..HEAD push on reference is experimental at /home/simon/dev/qtsdk/packaging-tools/create_changelog.pl line 107. keys on reference is experimental at /home/simon/dev/qtsdk/packaging-tools/create_changelog.pl line 151. Same in other modules. What am I missing? Simon ________________________________________ From: Development <development-bounces+simon.hausmann=theqtcompany....@qt-project.org> on behalf of Thiago Macieira <thiago.macie...@intel.com> Sent: Saturday, February 27, 2016 0:58 To: development@qt-project.org Subject: Re: [Development] change log creation tool (was: Re: Qt 5.6.0 missing change files) On sexta-feira, 26 de fevereiro de 2016 19:06:06 PST Hausmann Simon wrote: > Hi, > > It is different in three aspects: > > 1. It does not require passing git revision ranges as command line > parameters. So you have a heuristic algorithm that tries to guess the target version and which version was the last. You could have added this to the Perl script. > 2. It works on a per module basis instead of from the qt5 supermodule. So does the Perl script. > 3. It includes the task number from the commit message. So does the Perl script. So we gained the ability to run without being explicit which revisions we want, but now we need to install a compiler we didn't use before and compile code? -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
