public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mikael Hallendal <hallski@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] gentoo-ebuild->incoming move
Date: 06 Dec 2001 07:10:52 +0100	[thread overview]
Message-ID: <1007619052.6862.9.camel@fry> (raw)
In-Reply-To: <200112051923.BBK19889@mirapoint.inter.net.il>

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

ons 2001-12-05 klockan 20.24 skrev Dan Armak:
> Hi everyone,
> 
> Drobbins told me to put all the gentoo-ebuild luggage into incoming, even 
> though dev-wiki is down and there'll be no notes. So I'm going to do just 
> that. Once I'm finished, incoming will contain as many as 60+ ebuilds. Hope 
> someone can make good use of them all!
> 
> (Hurry with the issue tracking decision, wherever it's stuck this time)

Agreed, how's it going Kabau?

We really need something setup soon, the incoming directory is a really
bad way of handling this.

Regards,
  Mikael Hallendal

-- 

Mikael Hallendal
Gentoo Linux Developer, Desktop Team Leader
CodeFactory AB, Stockholm, Sweden


[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-12-06  6:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-05 19:24 [gentoo-dev] gentoo-ebuild->incoming move Dan Armak
2001-12-06  6:10 ` Mikael Hallendal [this message]
2001-12-06 16:06   ` Damon M. Conway
2001-12-06 17:55     ` Joshua Pollak
2001-12-06 18:02       ` Damon M. Conway
2001-12-08  1:46       ` Mikael Hallendal
     [not found]       ` <20011211213842.241261A4D1@chiba.3jane.net>
2001-12-13 18:15         ` [gentoo-dev] Pest issue tracker demo Joshua Pollak
2001-12-13 20:21           ` Mikael Hallendal
2001-12-13 20:58             ` Joshua Pollak
2001-12-13 23:46               ` Mikael Hallendal
     [not found]         ` <E16EaOy-0000bM-00@smtp6.mindspring.com>
2001-12-13 18:22           ` [gentoo-dev] " Damon M. Conway

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=1007619052.6862.9.camel@fry \
    --to=hallski@gentoo.org \
    --cc=gentoo-dev@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