public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexander Berntsen <alexander@plaimi.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Vanilla sources stabilization policy change
Date: Mon, 29 Jul 2013 23:45:32 +0200	[thread overview]
Message-ID: <51F6E27C.9080303@plaimi.net> (raw)
In-Reply-To: <51F3CBF7.1080705@gentoo.org>

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

On 27/07/13 15:32, Manuel Rüger wrote:
> On 07/27/2013 03:28 PM, Alexander Berntsen wrote:
>> Then we might as well just have a Linux package with a bunch of 
>> USE flags -- gentoo, hardened, libre, tuxonice, ck, etc.
> This is not a good idea, I'd like to have different kernel
> flavours of the same version installed in parallel.

On 27/07/13 20:20, Chí-Thanh Christopher Nguyễn wrote:
> I don't think this can be made work, the other kernel packages' 
> releases may not happen simultaneously with kernel releases. Or
> they may even skip certain releases.

Sorry, the point I was trying to make was basically that I think that
using a "vanilla" USE flag is a bad idea.

- -- 
Alexander
alexander@plaimi.net
http://plaimi.net/~alexander
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iF4EAREIAAYFAlH24nsACgkQRtClrXBQc7UfUAEAr465o/VCLPTvYLMEQ4aZMO9S
8b6HyeAqYp1HRVgg5usBAK4n4j2hgw/6JzFFfEJyOZWIvWC4tEQyffj8p62BP35/
=64DS
-----END PGP SIGNATURE-----


  reply	other threads:[~2013-07-29 21:45 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-24 14:02 [gentoo-dev] Vanilla sources stabilization policy change Mike Pagano
2013-07-24 17:37 ` Peter Stuge
2013-07-24 17:43   ` Alex Xu
2013-07-24 17:46     ` Rich Freeman
2013-07-24 17:54       ` Peter Stuge
2013-07-24 18:25         ` Rich Freeman
2013-07-24 19:01           ` Peter Stuge
2013-07-24 19:10             ` Ben Kohler
2013-07-24 19:15               ` Peter Stuge
2013-07-24 20:40                 ` Tom Wijsman
2013-07-24 20:40                 ` Rich Freeman
2013-07-24 20:45                   ` Ciaran McCreesh
2013-07-24 23:09                   ` Greg KH
2013-07-25  1:42                     ` Rich Freeman
2013-08-07  9:37                     ` Tom Wijsman
2013-08-07 22:44                       ` Greg KH
2013-08-07 22:50                         ` Peter Stuge
2013-08-07 23:19                           ` Greg KH
2013-08-08  2:43                             ` Tom Wijsman
2013-08-08 22:29                               ` Greg KH
2013-08-09  8:10                                 ` Tom Wijsman
2013-08-08 23:44                             ` Peter Stuge
2013-08-09  8:23                               ` Tom Wijsman
2013-08-08  2:37                         ` Tom Wijsman
2013-08-08 22:32                           ` Greg KH
2013-08-09  8:34                             ` Tom Wijsman
2013-08-09 10:38                               ` Rich Freeman
2013-08-09 13:28                                 ` Tom Wijsman
2013-08-09 19:27                                   ` Greg KH
2013-08-09 19:30                               ` Greg KH
2013-08-09 19:46                                 ` Tom Wijsman
2013-08-09 19:57                                   ` Greg KH
2013-07-24 20:22             ` Tom Wijsman
2013-07-24 20:06         ` Tom Wijsman
2013-07-24 17:49     ` Peter Stuge
2013-07-24 17:58       ` Alex Xu
2013-07-24 18:16         ` Peter Stuge
2013-07-24 20:59           ` Tom Wijsman
2013-07-24 22:17             ` Markos Chandras
2013-08-07  9:47               ` Tom Wijsman
2013-07-27  8:02           ` Sergey Popov
2013-07-27  8:56 ` Chí-Thanh Christopher Nguyễn
2013-07-27 13:28   ` Alexander Berntsen
2013-07-27 13:32     ` Manuel Rüger
2013-07-29 21:45       ` Alexander Berntsen [this message]
2013-08-07  9:58       ` Tom Wijsman
2013-07-27 18:20     ` Chí-Thanh Christopher Nguyễn
2013-07-27 13:58   ` Rich Freeman
2013-07-27 18:55     ` Mike Pagano

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=51F6E27C.9080303@plaimi.net \
    --to=alexander@plaimi.net \
    --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