[Libreoffice] Windows build tagging ...

Bjoern Michaelsen bjoern.michaelsen at canonical.com
Thu Oct 27 18:47:38 PDT 2011

Christian Lohmaier <lohmaier+libreoffice at ...> writes:

> So I suspect the --set-last-working shall be limited to the
> tinderboxes that build regularly with a non-changing setup, i.e.
> without having random other stuff that might affect the build-result?

Well, as long as we would only set last-working and ignore broken commits
I dont think it would matter to much. However, if one indeed uses notes one
could also add autogen.lastrun and the compiler version on the third line ... 

> never used the notes feature - but its help says that it can list the
> notes - so no parsing of the full log necessary, just using "git notes
> list" and iterate the list of note-object until the "magic string" is
> found, and then checkout the corresponding annotated object.

That would break when we have those notes on multiple branches (master and
release branch), which is quite likely. We are interested only in stable
commits on the current branch, I guess.

> The annotated commit is extracted from the "+++ b/<commit-hash>" line

--pretty spares you most of the parsing-foo.



More information about the LibreOffice mailing list