public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH 0/4] Autounmask changes
Date: Wed, 13 Aug 2014 09:45:32 -0700	[thread overview]
Message-ID: <20140813094532.6ba40f8f.dolsen@gentoo.org> (raw)
In-Reply-To: <53EB8D23.20208@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Wed, 13 Aug 2014 18:06:59 +0200
Alexander Berntsen <bernalex@gentoo.org> wrote:
 
> Evidently Michał was a bit sceptical. And anyway, I don't care too
> much about these patches any longer. Maybe it comes with raising in
> the ranks, but 2014 me is not particularly sympathetic of 2013 me and
> his stupid patches. These days I just prefer fixing bugs and not
> changing anything.
> 
> So on that note, if nobody objects, I suggest we just ignore the
> autounmask refactor altogether. Instead I'll just make the actual
> bugfix (make --ask imply --autounmask-write) a standalone patch which
> I'll submit to the list. Sounds good to everyone?
> - -- 
> Alexander
> bernalex@gentoo.org


Actually, re-reading your patches again, your patches actually made
more sense to me finally.  You were fixing it to make implied
behavior the actual behavior.  So while I was originally objecting to
them, then was not opposing them (last time we discussed inclusion), I
now see them much clearer and agree with them.

The --ask implying --autounmask-write is something people would not
object to so strongly like they did to your original patchset. 

- -- 
Brian Dolbec <dolsen>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQF8BAEBCgBmBQJT65YtXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4Njg4RkQxQ0M3MUMxQzA0RUFFQTQyMzcy
MjE0RDkwQTAxNEYxN0NCAAoJECIU2QoBTxfLgYQIAL2ziseGyyepSZmHQkFUTuEh
cSgmc+Gm/JcUXXxHycJ9F2GGFBFiVlIsItyrOkzXDHzkJmXaJCg9dUgUYaJPVdE4
IK2wR9mwVi9kcJE0r7sBKhtj2yeUYajGxD85AHzQHqtcaZSnQ7DC2oqLS0ZyDg2B
nc+yks9HRdAczQrg3As/BVX4bwzD6irAKrfVAcdG0JeB2lVUodrZzON2r24qzzi7
lubgcnSyxQQ4Yot25H6rrKlsv1JQR7e9QSMlQQJJ6FhB5DzY6OsQua+/Daod60AP
LjqLA7zNL8DvzVFmWK/3GQSTdabBN/XBteTABJ1ZZY/EJi5IfP5PHYnbqvK27aY=
=2Pok
-----END PGP SIGNATURE-----

  reply	other threads:[~2014-08-13 16:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-12  9:37 [gentoo-portage-dev] [PATCH 0/4] Autounmask changes Alexander Berntsen
2014-08-12  9:37 ` [gentoo-portage-dev] [PATCH 1/4] emerge: Deprecate --autounmask Alexander Berntsen
2014-08-12  9:37 ` [gentoo-portage-dev] [PATCH 2/4] emerge: Rename --autounmask-write to --autounmask Alexander Berntsen
2014-08-12  9:37 ` [gentoo-portage-dev] [PATCH 3/4] emerge: Make --autounmask=y if --ask=y Alexander Berntsen
2014-08-12  9:37 ` [gentoo-portage-dev] [PATCH 4/4] emerge: Let --autounmask=n override other options Alexander Berntsen
2014-08-13 16:06 ` [gentoo-portage-dev] [PATCH 0/4] Autounmask changes Alexander Berntsen
2014-08-13 16:45   ` Brian Dolbec [this message]
2014-08-13 16:56     ` Alexander Berntsen
2014-08-13 17:59       ` [gentoo-portage-dev] " Duncan
2014-08-13 18:39         ` Alexander Berntsen
2014-08-13 19:24         ` Wyatt Epp
2014-08-13 19:39           ` Alexander Berntsen

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=20140813094532.6ba40f8f.dolsen@gentoo.org \
    --to=dolsen@gentoo.org \
    --cc=gentoo-portage-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