On Mon, Feb 7, 2011 at 10:29 AM, Michael Meeks <michael.meeks@novell.com> wrote:
On Sun, 2011-02-06 at 05:44 -0600, Norbert Thiebaud wrote:
Note that the main drawback of our current approach is indeed the
bisection problem. It would be certainly be convinient to be able to
bisect on the entire set of repos... but how much pain/risk do we want
to take to improve that aspect of things ?
Could we do some sort of date based bisection ? or does that not work
because the patches are not in chronological order really ;-)
Even if we could rely on a date (which we can't), that would give you
the starting point. the bisection after that is just
a bisection of the commit between that point and HEAD (usually)
the problem is that we have commit scattered across 20 git repos... so in order
to truly bisect, we need an extra layer to 'serialized' all the commit
from all the git repos, and then bisect that series of commit
Norbert
Hmm,
Michael.
--
michael.meeks@novell.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.