On Fri, 2011-12-02 at 10:25 +0100, Thorsten Behrens wrote:
The list of fixed bugs in this release is here:
http://dev-builds.libreoffice.org/pre-releases/src/bugfixes-master-release-3.5.0.0.log
(warning, monstrous list - a lot has happened since April)
So - I assume this is generated from a git log command. Unfortunately
the onegit merge makes it ~impossible to get a sane git log from our
previous release tags. As you go over the mergepoint we end up with all
the merged commits from the other branches :-)
Luckily, I spent quite some time fixing this already for our commit
statistics (which were also busted by this). So
gitdm-config/analyse_commits has a chunk of perl that:
* fetches git notes
* parses all note comments to find the per repo. merge
revisions.
* runs log commands between the relevant tags
per repository from each repo's start-point[1]
to the pre-merge-point, and from post-mergepoint to now
It is not entirely trivial ;-) it's prolly worth taking the above list
down until we have something more accurate, which may take some time.
HTH,
Michael.
[1] - adapting analyse_commits to work only on log messages, and to work
instead from a repo-specific version tag on each branch is prolly fairly
trivial
--
michael.meeks@suse.com <><, Pseudo Engineer, itinerant idiot
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.