public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Karl Trygve Kalleberg <karltk@prosalg.no>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] dev-lisp
Date: Sun Aug  5 18:23:01 2001	[thread overview]
Message-ID: <20010806022205.C25475@prosalg.no> (raw)
In-Reply-To: <01080310182907.00608@localhost>; from danarmak@gentoo.org on Fri, Aug 03, 2001 at 10:18:29AM +0300

On Fri, Aug 03, 2001 at 10:18:29AM +0300, Dan Armak wrote:

> If you haven't yet, please move the ebuilds you submitted here from incoming 
> to their rightful places and grab their items on dev-wiki. There's only one 
> left there I think, python-docs.

Chadh already grabbed this one. 

Also, would it not be a good idea for another team member than the
original submitter to grab the item and do the actual verification and
move ?

This way, we get at least a minimum of "code-review" before the script is
sent off into the dangerous Real World.


Regards,

Karl T



  reply	other threads:[~2001-08-06  0:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-02 20:08 [gentoo-dev] dev-lisp Karl Trygve Kalleberg
2001-08-02 22:12 ` Daniel Robbins
2001-08-03  1:20 ` Dan Armak
2001-08-05 18:23   ` Karl Trygve Kalleberg [this message]
2001-08-03  6:53 ` Terje Kvernes

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=20010806022205.C25475@prosalg.no \
    --to=karltk@prosalg.no \
    --cc=gentoo-dev@cvs.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