public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in media-sound/umurmur: metadata.xml ChangeLog
Date: Thu, 26 Dec 2013 12:59:39 -0600	[thread overview]
Message-ID: <20131226125939.082376a8@caribou> (raw)
In-Reply-To: 52BB17D4.6040907@gentoo.org

[-- Attachment #1: Type: text/plain, Size: 1605 bytes --]

On Wed, 25 Dec 2013 18:37:24 +0100
Patrick Lauer <patrick@gentoo.org> wrote:

> On 12/25/2013 01:26 PM, hasufell wrote:
> 
> > You are interfering with my workflow and I already told you why I kept
> > the useflag, so stop reverting my commits after I told you the reasons
> > in a private mail.
> > 
> > QA is more than just running repoman and doing random commits on other
> > peoples ebuilds. (besides that you already managed to break the
> > Manifest of this stable package last time)
> > 
> 
> Soooooooooooo ....
> 
>   25 Dec 2013; Julian Ospald <hasufell@gentoo.org> metadata.xml:
>   revert pseudo-QA commit
> 
>   25 Dec 2013; Patrick Lauer <patrick@gentoo.org> metadata.xml:
>   Remove unneeded useflag description from metadata.xml
> 
>   23 Dec 2013; Julian Ospald <hasufell@gentoo.org> metadata.xml:
>   add unused useflag since the breakage is expected to be temporary
> 
> 
> <irker104> AutoRepomanReport for Wed Dec 25 17:22:16 UTC 2013
> <irker104> AutoRepomanWarning: media-sound/umurmur/metadata.xml: unused
> local USE-description: 'polarssl'
> 
> 
> Why the bleeping bleep are you KNOWINGLY introducing a useless
> regression that serves no purpose but to annoy some people, and then add
> a passive-agressive Changelog entry?
> 
> Fix your workflow, man ... and don't cause useless warning spam if you
> can avoid it.

Oh FFS it's a USE flag.  You guys have bigger fish to fry.


-- 
Ryan Hill                        psn: dirtyepic_sk
   gcc-porting/toolchain/wxwidgets @ gentoo.org

47C3 6D62 4864 0E49 8E9E  7F92 ED38 BD49 957A 8463

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

      reply	other threads:[~2013-12-26 18:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20131225095020.A91BE2004C@flycatcher.gentoo.org>
2013-12-25 12:26 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in media-sound/umurmur: metadata.xml ChangeLog hasufell
2013-12-25 12:42   ` Tom Wijsman
2013-12-25 13:16   ` Patrick Lauer
2013-12-25 13:30     ` Kent Fredric
2013-12-26 13:25     ` hasufell
2013-12-26 13:27       ` Ciaran McCreesh
2013-12-26 13:29         ` hasufell
2013-12-26 13:53           ` Patrick Lauer
2013-12-27  0:52         ` vivo75
2013-12-28 15:11         ` Markos Chandras
2013-12-28 15:44           ` Andreas K. Huettel
2013-12-28 15:44             ` Markos Chandras
2013-12-28 16:50               ` Tom Wijsman
2013-12-28 18:35               ` hasufell
2013-12-28 16:35           ` Tom Wijsman
2013-12-28 17:26             ` Patrick Lauer
2013-12-28 18:12               ` Tom Wijsman
2013-12-26 17:20     ` Lars Wendler
2013-12-25 17:37   ` Patrick Lauer
2013-12-26 18:59     ` Ryan Hill [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131226125939.082376a8@caribou \
    --to=dirtyepic@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox