public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: foser <foser@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last rites for dev-util/cccc
Date: Tue, 18 Apr 2006 17:13:45 +0200	[thread overview]
Message-ID: <1145373225.18478.51.camel@rivendell> (raw)
In-Reply-To: <200604181053.01775.vapier@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 505 bytes --]

On Tue, 2006-04-18 at 10:53 -0400, Mike Frysinger wrote:
> dont know what policy you're referring to seeing as how we dont have any 
> concerning unmaintained packages

Still hiding... c'mon you are better than this.

> sure, for new packages ... cccc isnt a new package

The policy concerning metadata makes no difference between
new/(un)maintained. It just says that every package should have one. So
if you come across a pack that doesn't and you touch it, you need to fix
that.

- foser

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-04-18 15:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-15  4:49 [gentoo-dev] Last rites for dev-util/cccc Mark Loeser
2006-04-15  6:54 ` Mike Frysinger
2006-04-15 10:55   ` foser
2006-04-15 16:07     ` Mark Loeser
2006-04-15 17:46       ` Chris Bainbridge
2006-04-15 18:24       ` Mike Frysinger
2006-04-16 15:17         ` foser
2006-04-16 20:42           ` Mike Frysinger
2006-04-18 11:00             ` foser
2006-04-18 13:11               ` Chris Bainbridge
2006-04-18 13:51                 ` foser
2006-04-18 14:22                   ` Mike Frysinger
2006-04-18 14:41                     ` foser
2006-04-18 14:53                       ` Mike Frysinger
2006-04-18 15:13                         ` foser [this message]
2006-04-18 14:56                       ` Philippe Trottier
2006-04-18 15:16                         ` foser
2006-04-18 16:13                           ` Philippe Trottier
2006-04-18 14:21               ` Mike Frysinger

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=1145373225.18478.51.camel@rivendell \
    --to=foser@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