On Fri, Dec 9, 2011 at 5:20 AM, Pedro Lino <pedl...@gmail.com> wrote: >> But developers don't commit to the central repository. They commit to >> their local "clones" of it, and then at some (much) later stage push >> outstanding commits to the central repository. And then there are >> feature branches and merges... > > Ok. Wrong wording. What I meant was "the time a change was pushed to > the central repository by a developer" which is comparable to the pull > time from the central repository.
the problem is that this 'time' is not recorded anywhere. git does not keep track of it. So the only way to be 'certain' is to use sha1 and git log to compare where the sha1 of the build you test is compared to the dha1 of the alledge fix. It is possible to do a web service to automate that (that is giving 2 sha1s and it tell you if the second one (the fix) is an 'ancestor' of the first one (your build) essentially: if $(git merge-base <build-sha> <fix-sha>) = <fix-sha> Norbert _______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
