Some extension commits go past Gerrit code review. This means that it
is impossible to even get notifications on those extensions. Some of
those extensions are in use at translatewiki.net and given the
numerous breakages related to those extensions lately, I am seriously
considering removing
Am 21.05.2012 18:41, schrieb Marcin Cieslak:
I have a question here since I am not sure I fully understand the problem:
how are you getting notifications that i18n files have changed?
From gerrit or git? I think it should be the latter (some git hook).
From Gerrit. Manually opening every
On Fri, May 18, 2012 at 3:53 AM, Niklas Laxström
niklas.laxst...@gmail.com wrote:
About a month ago it seemed like that things were heading to the right
direction: we had working l10n commit auto-merging and
LocalisationUpdate running. That only lasted couple of days and since
then things have
Hey,
I'm working on a way for auto-approving
Thanks for all your work on the git stuff :)
of extensions that don't want to be reviewed.
I hope there are very few people that do not want review for their
extensions. However, this is not why people need to have automatic merging.
The use case
On Sun, May 20, 2012 at 12:38 PM, Jeroen De Dauw jeroended...@gmail.com wrote:
I hope there are very few people that do not want review for their
extensions. However, this is not why people need to have automatic merging.
The use case is people developing extensions and not being able to wait
On Sun, May 20, 2012 at 12:55 PM, Chad innocentkil...@gmail.com wrote:
PS: Here's the default review rules
http://code.google.com/p/gerrit/source/browse/gerrit-server/src/main/prolog/gerrit_common.p
Make that
On Sun, May 20, 2012 at 1:15 PM, Jeremy Baron jer...@tuxmachine.com wrote:
On Sun, May 20, 2012 at 12:55 PM, Chad innocentkil...@gmail.com wrote:
PS: Here's the default review rules
http://code.google.com/p/gerrit/source/browse/gerrit-server/src/main/prolog/gerrit_common.p
Make that
On 20/05/12 19:15, Jeremy Baron wrote:
On Sun, May 20, 2012 at 12:55 PM, Chad innocentkil...@gmail.com wrote:
PS: Here's the default review rules
http://code.google.com/p/gerrit/source/browse/gerrit-server/src/main/prolog/gerrit_common.p
Make that
On Sun, May 20, 2012 at 1:45 PM, Platonides platoni...@gmail.com wrote:
On 20/05/12 19:15, Jeremy Baron wrote:
On Sun, May 20, 2012 at 12:55 PM, Chad innocentkil...@gmail.com wrote:
PS: Here's the default review rules
On 20/05/12 18:38, Jeroen De Dauw wrote:
Thinking about it, it would be nice to have a working post-commit review
workflow like we used to have, for those projects where gated trunk does
not work due to lack of quick review.
Cheers
gerrit seems to be all for pre-review, yet I think we
On Sun, May 20, 2012 at 5:13 PM, Platonides platoni...@gmail.com wrote:
Currently, there's no way to mark as fixme a revision which already got
into the repository.
There's also way to have followups (including reverts) with good
metadata and UI. You can make comments or commit msgs that
On Sun, May 20, 2012 at 9:38 AM, Jeroen De Dauw jeroended...@gmail.com wrote:
Thinking about it, it would be nice to have a working post-commit review
workflow like we used to have, for those projects where gated trunk does
not work due to lack of quick review.
Would it help if we implemented
About a month ago it seemed like that things were heading to the right
direction: we had working l10n commit auto-merging and
LocalisationUpdate running. That only lasted couple of days and since
then things have only gotten worse - neither auto-merge nor LU have
been reliably working for almost
On Fri, May 18, 2012 at 12:53 AM, Niklas Laxström niklas.laxst...@gmail.com
wrote:
I spent lots of hours on the week and weekend after the switch support
l10n commits to Gerrit. While doing that I modernized our repository
handling scripts, but the time savings those provide are negated by
14 matches
Mail list logo
