Re: [sipcore] #43: Small fixes
Paul Kyzivat <pkyzivat@cisco.com> Fri, 17 September 2010 20:37 UTC
Return-Path: <pkyzivat@cisco.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 502823A6870 for <sipcore@core3.amsl.com>; Fri, 17 Sep 2010 13:37:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.862
X-Spam-Level:
X-Spam-Status: No, score=-109.862 tagged_above=-999 required=5 tests=[AWL=-0.555, BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 40xaDstHsz2O for <sipcore@core3.amsl.com>; Fri, 17 Sep 2010 13:37:49 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 47BA93A6914 for <sipcore@ietf.org>; Fri, 17 Sep 2010 13:37:49 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAE9uk0xAZnwM/2dsb2JhbACDG546VXGneIoGkkOBIoMrcwSKM4J+
X-IronPort-AV: E=Sophos;i="4.56,384,1280707200"; d="scan'208";a="160588586"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 17 Sep 2010 20:38:13 +0000
Received: from [161.44.174.142] (dhcp-161-44-174-142.cisco.com [161.44.174.142]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o8HKcDsH010812; Fri, 17 Sep 2010 20:38:13 GMT
Message-ID: <4C93D1B5.5080007@cisco.com>
Date: Fri, 17 Sep 2010 16:38:13 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
References: <061.a01c95ac1b7d3fe52101cc609a7c57d3@tools.ietf.org>
In-Reply-To: <061.a01c95ac1b7d3fe52101cc609a7c57d3@tools.ietf.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: worley@alum.mit.edu, sipcore@ietf.org
Subject: Re: [sipcore] #43: Small fixes
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Sep 2010 20:37:51 -0000
(as chair *and* participant) I'm *really* not liking the way the issue tracker works - that the mail subject doesn't say what draft the issue relates to. What do other people think about that? Is anybody an expert on the tracker? Is there some way to configure it to put the component name into the subject line? Thanks, Paul
- [sipcore] #43: Small fixes sipcore issue tracker
- Re: [sipcore] #43: Small fixes Paul Kyzivat
- Re: [sipcore] #43: Small fixes Mary Barnes
- [sipcore] Tracker usage policies Paul Kyzivat
- Re: [sipcore] Tracker usage policies Elwell, John
- Re: [sipcore] Tracker usage policies Worley, Dale R (Dale)