public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ian Stakenvicius <axs@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Stable sys-devel/gcc USE flag changes
Date: Tue, 15 Jan 2013 09:49:33 -0500	[thread overview]
Message-ID: <50F56C7D.5090303@gentoo.org> (raw)
In-Reply-To: <CAKmKYaBzC87CRQn5ReXx1-EU4qnv7YkuvLi20+oCMcZauBNyxw@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 15/01/13 09:39 AM, Dirkjan Ochtman wrote:
> 
> BTW, what happened with -u? I still use it because I'm used to it,
> but it seems to have gone away (i.e. I can't find it in the current
> man page).

It's there:
"
     --update (-u)
              Updates packages to the best version available, ...
"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iF4EAREIAAYFAlD1bH0ACgkQ2ugaI38ACPBl0AD/UF5lj7K1R65TWOcaaCf1NG41
dTPmGfvb6VldF4Fe+jUA/0uuZj1q51lYaylBQEP8TOrg8dZVlTLUsN02Fyr8S0g8
=qLlJ
-----END PGP SIGNATURE-----


  reply	other threads:[~2013-01-15 14:49 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130115023053.8897C2171E@flycatcher.gentoo.org>
2013-01-15  7:20 ` [gentoo-dev] Stable sys-devel/gcc USE flag changes WAS: [gentoo-commits] gentoo-x86 commit in eclass: ChangeLog toolchain.eclass Michael Weber
2013-01-15 13:44   ` [gentoo-dev] Stable sys-devel/gcc USE flag changes Ian Stakenvicius
2013-01-15 14:03     ` Rich Freeman
2013-01-15 14:16       ` Dirkjan Ochtman
2013-01-15 14:27         ` Ian Stakenvicius
2013-01-15 14:39           ` Dirkjan Ochtman
2013-01-15 14:49             ` Ian Stakenvicius [this message]
2013-01-15 14:53             ` Ian Stakenvicius
2013-01-15 15:24             ` Rich Freeman
2013-01-15 20:18               ` Peter Stuge
2013-01-15 20:51                 ` Dirkjan Ochtman
2013-01-16 16:36                   ` Michael Weber
2013-01-16 16:47                     ` Michael Orlitzky
2013-01-16 16:49                       ` Michael Orlitzky
2013-01-16 17:24                         ` Ian Stakenvicius
2013-01-16 17:33                           ` Michael Orlitzky
2013-01-17  0:00                             ` Michael Weber
2013-01-17  3:24                               ` Rich Freeman
2013-01-17 14:45                                 ` Peter Stuge
2013-01-17 14:58                                 ` Ian Stakenvicius
2013-01-17 14:46                               ` Zac Medico
2013-01-16 17:24                       ` Ian Stakenvicius
2013-01-16 17:32                         ` Michael Orlitzky
2013-01-17 14:52                           ` Zac Medico
2013-01-17 16:31                             ` Michael Orlitzky
2013-01-17 17:11                               ` Ian Stakenvicius
2013-01-17 17:33                                 ` Michael Orlitzky
2013-01-17 23:55                               ` [gentoo-dev] " Duncan
2013-01-16  2:20   ` [gentoo-dev] Re: Stable sys-devel/gcc USE flag changes WAS: [gentoo-commits] gentoo-x86 commit in eclass: ChangeLog toolchain.eclass Ryan Hill
2013-01-18  7:27   ` update commands / world file pollution Re: [gentoo-dev] " Michael Weber
2013-01-18  7:36     ` Benedikt Böhm
2013-01-18  8:13       ` Michael Weber
2013-01-18  8:28         ` Benedikt Böhm
2013-01-18  8:41           ` Michael Weber
2013-01-18 13:13             ` Benedikt Böhm
2013-01-18 13:18               ` Benedikt Böhm
2013-01-18 13:25         ` Ian Stakenvicius

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=50F56C7D.5090303@gentoo.org \
    --to=axs@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