Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


Jan Holesovsky wrote
...
I thought perhaps it could be interesting to have a file in addition to
build info (or perhaps inside it?)  which gives the list of commits
retrieved since the previous build.
I read too  https://bugs.freedesktop.org/show_bug.cgi?id=65653#c30 which
indicates "git branch --contains 
<commit>
" but you must have git +  git repo
up-to-date in local.

Any idea?

The build has the git commit id in the About box, you can just do git
log that_commit_id in your tree, or go to

http://cgit.freedesktop.org/libreoffice/core/commit/?id=that_commit_id
...

Hi Jan,

I meant for someone who doesn't have git so for the tree I don't think it
would help.

About cgit, you can include the commit id of the build then of the patch and
afterwards compare the results retrieved  (that's what I would do if I need)
but it's not very practical.

If the list isn't possible (or quite difficult to implement), at least it
could be useful to have the syntax to give a range to cgit (or perhaps
possible with gerrit?). Indeed, almost each time i put a "-", I've got an
"Internal Server error" and in the other cases, I've got no result found.
There must be a trick I don't know :-)

Julien



--
View this message in context: 
http://nabble.documentfoundation.org/Just-a-suggestion-for-Tinderbox-tp4061929p4062034.html
Sent from the Dev mailing list archive at Nabble.com.

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.