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


Hi Bjoern,

Bjoern Michaelsen píše v Pá 03. 05. 2013 v 18:19 +0200:

Well, yeah. And when we wait half a day, we could also collect all the unpushed
fixes in _one_ mail and not start one thread for each. We could go fancy and
call this mail "digest". ;)

Digest with N patches in a lump kills the possibility to scan the
content quickly, so wouldn't work for anybody, and would be just a
waste.

I dont see the need to track the status of patches via flaky "PUSHED" "PATCH"
subjects of emails -- at least for patches on gerrit, gerrit has a much better
way of keeping track of things as it tracks and watches the repository directly.

Those who merge most of the patches should decide what works for them
best I believe.  Definitely it is not me, so I actually apologize for
promoting my workflow, but it's easy to find out using

OLD="" ; COUNT=0 ; git log | grep 'Reviewed-by:' | sort | while read NAME ; do if [ "$OLD" != 
"$NAME" ] ; then echo "$COUNT $OLD" ; OLD="$NAME" ; COUNT=0 ; fi ; COUNT=$(($COUNT+1)) ; done | 
sort -r -n

that the 10 most active are Caolán, Fridrich, Thomas, Michael S.,
Norbert, Miklos, David T., Tor, Andras, Olivier.

Also consider the long tail here - how do you want to grow the amount of
people who merge patches, when it will be hidden in gerrit only or a
different / not default mailing list?

All the best,
Kendy


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.