public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tom Wijsman <TomWij@gentoo.org>
To: hasufell@gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in media-sound/umurmur: metadata.xml ChangeLog
Date: Wed, 25 Dec 2013 13:42:58 +0100	[thread overview]
Message-ID: <20131225134258.66b987c2@TOMWIJ-GENTOO> (raw)
In-Reply-To: <52BACEE8.1010006@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 25 Dec 2013 13:26:16 +0100
hasufell <hasufell@gentoo.org> 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.

Interference goes both ways, that's why both of you are reverting; if
you mask the USE flag then you can keep the description, it is more
preferable than removing the flag from the ebuild (that is even stable).

> 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)

QA is that it is written down (as a mask) that the USE flag is broken;
removing it just hides its brokenness, it might very well fit in your
workflow but if someone else joins maintenance or the package gets
maintained by someone else later "out of sight, out of mind" applies.

- -- 
With kind regards,

Tom Wijsman (TomWij)
Gentoo Developer

E-mail address  : TomWij@gentoo.org
GPG Public Key  : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2  ABF0 95B2 1FCD 6D34 E57D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJSutLSAAoJEJWyH81tNOV9C3MIAKH8JzNIHpAXH8esAKe3EtQ5
HFJDHBPxjfBiAN2IB442rqjH3cfFHPI6EBb4ULb2TRIW2kgTyIGsUrmaPtONm9td
EYT+kAWlyh9OVRHlJ1jYoB2UTixBrdVaNApiMojJ9Uvn3yukSaDf7mW0rf9jxPv3
+92XjmuqTiPybC2qyp/nl6HNXoQ8TfQd+nLZiQm3AWXBR3hhiHDOUrMUlsdHmGFs
qlYMk529NFCGSFENBvooT3xSKUazXe+pjN06TycY9DKk2199dPWOeVYwIAlY1KqW
cuWyj/gqCMo7RSku+lkl/OKkn1NsIAvoA+IKBECjpdgD1/kPVdt6iBapDqh6RHI=
=E8a/
-----END PGP SIGNATURE-----

  reply	other threads:[~2013-12-25 12:43 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 [this message]
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

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=20131225134258.66b987c2@TOMWIJ-GENTOO \
    --to=tomwij@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=hasufell@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