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


Hi Sebastian,

On Fri, 2012-06-22 at 16:03 +0200, Sebastian Spaeth wrote:
Hi all, I was annoyed by the oververbose gerrit query output so I fixed
it for me.

        Me too :-)

I learned too late that David has something similar as logerrit
in the core repository. But it is in shell script, and I have written a
small query helper in python. It lists outstanding patches similar to
"git log" (it also uses less to show them). The output is like this:

        Could we not convert David's logerrit into python ? and have a single
script in more of a real programming language :-) [ shell eventually
becomes an un-maintainable / non-portable tangle IMHO ].

        David - would you be ok with that ?

The code is at git://gitorious.org/querrit/querrit.git and requires
Python3.

        Oh - but of course requiring the very latest python is not so cool for
general use I guess :-)

Feedback is welcome. I plan to add some config file support to be able
to configure the hostname. If I have plenty of time, I'll also add a
userfriendly "review" tool.

        Sounds great to me, but I'd -love- us all using, documenting, and
improving the same tooling (preferably not written in shell) ;-)

        Thanks for jumping on and fixing the problem :-)

        All the best !

                Michael.

-- 
michael.meeks@suse.com  <><, Pseudo Engineer, itinerant idiot


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.