Re: [http-state] getting an issue tracker up at tools.ietf.org?
=JeffH <Jeff.Hodges@KingsMountain.com> Tue, 15 December 2009 23:26 UTC
Return-Path: <Jeff.Hodges@KingsMountain.com>
X-Original-To: http-state@core3.amsl.com
Delivered-To: http-state@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D2D5C3A68DC for <http-state@core3.amsl.com>; Tue, 15 Dec 2009 15:26:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.857
X-Spam-Level:
X-Spam-Status: No, score=-1.857 tagged_above=-999 required=5 tests=[AWL=-1.081, BAYES_05=-1.11, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xmA9vxJp7SdP for <http-state@core3.amsl.com>; Tue, 15 Dec 2009 15:26:42 -0800 (PST)
Received: from outbound-mail-110.bluehost.com (outbound-mail-110.bluehost.com [69.89.22.10]) by core3.amsl.com (Postfix) with SMTP id CC6D63A677E for <http-state@ietf.org>; Tue, 15 Dec 2009 15:26:41 -0800 (PST)
Received: (qmail 23049 invoked by uid 0); 15 Dec 2009 23:26:28 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by outboundproxy3.bluehost.com with SMTP; 15 Dec 2009 23:26:28 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kingsmountain.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=gl94m9pHUZb7V6aCT+x3NxXqNkFhCLSJGEXihgd/PTIKU/ogg5xU2kxdiZGB+/Tez6OY75AtXlG26tEnHdNO6yDZ/Zxfg5IU9/6pDu6sfe/AgMZc+zs1Pt05RUVcaxFA;
Received: from outbound4.ebay.com ([216.113.168.128] helo=[10.244.48.58]) by box514.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1NKgmi-0003qK-3Y for http-state@ietf.org; Tue, 15 Dec 2009 16:26:28 -0700
Message-ID: <4B281B29.1070402@KingsMountain.com>
Date: Tue, 15 Dec 2009 15:26:33 -0800
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Thunderbird 1.5.0.14ubu (X11/20080306)
MIME-Version: 1.0
To: IETF httpstate WG <http-state@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com} {sentby:smtp auth 216.113.168.128 authed with jeff.hodges+kingsmountain.com}
Subject: Re: [http-state] getting an issue tracker up at tools.ietf.org?
X-BeenThere: http-state@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discuss HTTP State Management Mechanism <http-state.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/http-state>, <mailto:http-state-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/http-state>
List-Post: <mailto:http-state@ietf.org>
List-Help: <mailto:http-state-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/http-state>, <mailto:http-state-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Dec 2009 23:26:43 -0000
> By the way, do you know what's involved in getting an issue tracker up > and running at tools.ietf.org? I am wondering that too. I've queried tools-discuss@ about this. =JeffH