public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: cilly <cilly@cilly.mine.nu>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Do not modify ebuilds which are already in the tree... even if masked
Date: Tue, 12 Jun 2007 12:28:18 +0200	[thread overview]
Message-ID: <446AE7A9-D092-4A71-9B92-BB11B29C6321@cilly.mine.nu> (raw)
In-Reply-To: <466E7355.2050807@gentoo.org>

On Jun 12, 2007, at 12:20 PM, Petteri Räty wrote:

> http://devmanual.gentoo.org/general-concepts/ebuild-revisions/ 
> index.html
>
> This is the current policy. So far it has worked quite well for me  
> at least.

Okay, does this include ~ packages? And what about hard masked ones?--
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2007-06-12 10:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-12 10:07 [gentoo-dev] Do not modify ebuilds which are already in the tree... even if masked cilly
2007-06-12 10:16 ` Fernando J. Pereda
2007-06-12 10:20 ` Petteri Räty
2007-06-12 10:28   ` cilly [this message]
     [not found]     ` <200706121414.55040.carlo@gentoo.org>
2007-06-12 12:30       ` Sorry! WAS: " cilly
2007-06-12 10:21 ` Luca Barbato
2007-06-12 10:26   ` cilly
2007-06-12 10:55 ` Marius Mauch
2007-06-12 11:43   ` cilly
     [not found]     ` <20070612135602.25988df6@luna.home>
2007-06-12 12:01       ` [gentoo-dev] " cilly
2007-06-12 12:05       ` cilly
2007-06-12 12:17         ` Luca Barbato
2007-06-12 12:29           ` Markus Ullmann
     [not found]     ` <20070612135625.6e5a501a@loki>
2007-06-12 12:08       ` [gentoo-dev] " cilly
2007-06-13 12:50         ` [gentoo-dev] " Steve Long
2007-06-12 12:20     ` [gentoo-dev] " Michael Cummings
2007-06-12 11:50 ` Vlastimil Babka
2007-06-12 11:56   ` cilly
2007-06-12 12:05     ` [gentoo-dev] " Christian Faulhammer
2007-06-12 12:12       ` cilly
2007-06-12 12:37         ` Luca Barbato

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=446AE7A9-D092-4A71-9B92-BB11B29C6321@cilly.mine.nu \
    --to=cilly@cilly.mine.nu \
    --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