From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23316 invoked by alias); 21 Jul 2003 19:55:13 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 23309 invoked from network); 21 Jul 2003 19:55:13 -0000 Received: from unknown (HELO concert.shout.net) (204.253.184.25) by sources.redhat.com with SMTP; 21 Jul 2003 19:55:13 -0000 Received: from duracef.shout.net (duracef.shout.net [204.253.184.12]) by concert.shout.net (8.12.9/8.12.9) with ESMTP id h6LJtBLS017238; Mon, 21 Jul 2003 14:55:11 -0500 Received: from duracef.shout.net (localhost [127.0.0.1]) by duracef.shout.net (8.12.9/8.12.9) with ESMTP id h6LJtBHK022136; Mon, 21 Jul 2003 14:55:11 -0500 Received: (from mec@localhost) by duracef.shout.net (8.12.9/8.12.9/Submit) id h6LJtBPA022135; Mon, 21 Jul 2003 15:55:11 -0400 Date: Mon, 21 Jul 2003 19:55:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200307211955.h6LJtBPA022135@duracef.shout.net> To: ezannoni@redhat.com, gdb-patches@sources.redhat.com Subject: Re: [PATCH] fix info address for thread local vars X-SW-Source: 2003-07/txt/msg00379.txt.bz2 Hi Elena, > I am also really tempted to commit the tls tests (to the mailine > only), otherwise, the tls feature will bitrot. I'll work through > refining the tests once they are in. Could you file a PR like "tls tests not ready for prime time yet" and then shovel in a bunch of setup_kfail? It's cheesy but it might be better than letting the tests bit rot. What do people think? I'll even volunteer to sprinkle in the setup_kfail's if people think this is a useful idea. Michael C