[Libreoffice] Windows build tagging ...
michael.meeks at suse.com
Fri Oct 28 06:12:46 PDT 2011
On Fri, 2011-10-28 at 01:55 +0200, Christian Lohmaier wrote:
> 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 - I suggest we do it manually for now; at least something is
better than nothing here.
> 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
Sure, a good idea :-) I've been there; here is some sample output:
$ git notes list | head
Not so helpful in my view ;-)
> or if one wants to parse a log, one can do it with
> git log -p `git notes get-ref`
> that way one only has to examine the ones that match. or can do a
Sure - but the problem is then that you need to sort them into a
sequential /chronological order (which the notes list does not appear to
be in). At the end of the day - the 'git log' output is in the order we
want, and has the details ;-)
so - rest assured, I did think a little before suggesting this.
It seems like Bjoern's git log --pretty="%H %N" gives:
5ad4d151dac1eb887d92200330e31af269d8d1fd win32 working build
and is pretty much perfect on that basis :-)
So - will hack that into 'g' next week if no-one else has.
Thanks for the input !
michael.meeks at suse.com <><, Pseudo Engineer, itinerant idiot
More information about the LibreOffice