On Tue, 2013-08-13 at 10:10 +0200, Tomáš Chvátal wrote: > As per my comment in bugzilla [1] I said that the patch should be > submitted upstream prior having it in cvs. > > > Yet you decided to completely ignore my statement and just smash in > the patch anyway [2]. > > > Please don't do this ever again. We had shitload of distro patches > before and it is hell to strip away later on. > > > For your statement of lacking documentation, when I google gerrit > libreoffice first two links lead directly to the instance and 3rd to > wiki [3], which no suprise is guide how to set it up and submit > request, so stop lying. > > > As you like to ignore maintainer requests I now expect you to submit > it to the gerit, since now you have the guide and you can proceed > without an issue right? > > > Note that I have nothing against other devs submitting fixes to > ebuilds maintained by me, but directly ignoring what I said on a bug > and doing whatever you see fit does not match that at all. > > > Tomas > > > [1] https://bugs.gentoo.org/show_bug.cgi?id=479604#16 > [2] https://bugs.gentoo.org/show_bug.cgi?id=479604#19 > [3] https://wiki.documentfoundation.org/Development/gerrit
Tomáš, considering that libreoffice and libreoffice-bin were both broken on ~arch (so ~arch users did not have a compatible office suite to fall back on); the bug had 33 people in the CC list; a working patch was submitted, with a justification for why it is the correct solution, and was verified to work; and your response was (paraphrased) "I will look at this later" - I personally think that a small violation of openoffice team policies could in this particular case be forgiven. In addition, the policy itself is IMHO rather strange. If the goal is to ensure that any gentoo patch is visible to upstream developers and to libreoffice maintainers from other distros, so that they can merge it if they agree with the implementation, surely it would make no difference whether the patch got submitted to gerrit by Patrick before committing to gx86, or by you a week later? [1] On the other hand, if the goal is to avoid any divergence from upstream, presumably you want to first obtain feedback from upstream developers and an indication that they will merge the patch - in which case merely submitting something to gerrit, without waiting for upstream developer response, doesn't make sense. [1] on August 11, you had indicated that you would have time to look at the bug in ~10 days time.
