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


On 12/07/12 14:05, Lionel Elie Mamane wrote:
On Thu, Jul 12, 2012 at 11:45:34AM +0000, Gerrit wrote:

David Tardon has uploaded a new change for review.

Change subject: fdo#51278 make reportbuilder work again
......................................................................

fdo#51278 make reportbuilder work again

Change-Id: I46f970fa23a0afd54485efb58b7f4f757c7d7752

So, I'm trying to review that thing, but I get lost.

http://wiki.documentfoundation.org/Development/gerrit says:

 ./logerrit cherry-pick CHANGEID

This *obviously* answers
 -bash: ./logerrit: No such file or directory

and the above wiki page says nothing about downloading no "logerrit"
tool that would need... to be copied in the *current* directory for
each directory I want to work from? That's baroque.

it's in master branch.  the way i use it is that i just invoke it with
absolute path from the master branch git working tree that i already
have on my disk anyway.

So... What am I supposed to do (except find the git commit-id from
master and "git cherry-pick" that)?


another option is to use the web UI, click on the "cherry pick" button
and copy paste the command which looks like this:

git fetch https://gerrit.libreoffice.org/core refs/changes/96/296/1 &&
git checkout FETCH_HEAD

or i guess you can install git-review (there's a Fedora package for it
at least), but i haven't actually tried out how that works yet :)


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.