On Fri, Oct 28, 2011 at 3:12 PM, Michael Meeks <michael.meeks@suse.com> wrote:
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
list"
Sure, a good idea :-) I've been there; here is some sample output:
$ git notes list | head
63128339eb1c9dceab08cb9f34c8b3a6b278f48b 002c16ce95fa6e384e7541b6e656b9058dd9b459
3d98f2ca6d9843f7eecf3f8c8d85da2b3eb9e209 00a326249f7bb4e7ded9c743836d9d572d3a9d7f
de193bbe203f54b2cbb18d03962691b91a3b0b4c 00a6a3f6279dcf3b790a17f21bccd3e4cea1fc57
742a4d7cc15dda42a1acdab966994d39a9a0d991 010a4baa37bbdca0c35dc3555f6467174e956644
Not so helpful in my view ;-)
This is the notes list - show <first hash> and check for message, if
it is OK, checkout he <second hash>, but true:
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).
Git log on the notes object is not the same as git notes list.
the log is sequential/chronological as is any other commit.
At the end of the day - the 'git log' output is in the order we
want, and has the details ;-)
See above: "git *log* -p `git notes get-ref`" :-) and with the
additional -S earch you can filter that log output to only contain the
wanted ones.
git log -p -S"win32 working build" `git notes get-ref`
gives you only the annotation commits, and contains the annotated revision
I didn't just suggest things by only reading the manpage, I also
played with it....
ciao
Christian
Context
- Re: [Libreoffice] (real) Windows build, needs help. (continued)
[Libreoffice] Windows build tagging ... · Michael Meeks
Re: [Libreoffice] (real) Windows build, needs help. · Noel Grandin
Re: [Libreoffice] (real) Windows build, needs help. · Stephan Bergmann
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.