From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3509 invoked by alias); 21 May 2003 17:03:32 -0000 Mailing-List: contact ecos-maintainers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@sources.redhat.com Received: (qmail 3404 invoked from network); 21 May 2003 17:03:30 -0000 Subject: [Fwd: RE: Possible deadlock in serial.c] From: Gary Thomas To: eCos Maintainers Content-Type: multipart/mixed; boundary="=-OXp+k3MI92sNA8hpBFkB" Organization: MLB Associates Message-Id: <1053536609.1558.563.camel@hermes> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-4) Date: Wed, 21 May 2003 17:03:00 -0000 X-SW-Source: 2003-05/txt/msg00036.txt.bz2 --=-OXp+k3MI92sNA8hpBFkB Content-Type: text/plain Content-Transfer-Encoding: 7bit Content-length: 193 So, what is the expected policy? I can't see any of us spending tremendous resources trying to keep a release branch up-to-date. Comments? -- Gary Thomas MLB Associates --=-OXp+k3MI92sNA8hpBFkB Content-Disposition: inline Content-Description: Forwarded message - RE: Possible deadlock in serial.c Content-Type: message/rfc822 Content-length: 2074 Return-Path: Delivered-To: gary@chez-thomas.org Received: from localhost.localdomain [127.0.0.1] by localhost with POP3 (fetchmail-6.2.0) for gthomas@localhost (single-drop); Wed, 21 May 2003 10:53:03 -0600 (MDT) Received: from sources.redhat.com (sources.redhat.com [66.187.233.205]) by hermes.chez-thomas.org (Postfix) with SMTP id DF33B50E4F5 for ; Wed, 21 May 2003 10:52:29 -0600 (MDT) Received: (qmail 2915 invoked by alias); 21 May 2003 16:52:02 -0000 Mailing-List: contact ecos-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Post: List-Help: , Sender: ecos-patches-owner@sources.redhat.com Delivered-To: mailing list ecos-patches@sources.redhat.com Received: (qmail 2851 invoked from network); 21 May 2003 16:52:00 -0000 Message-ID: From: "David Marqvar (DAM)" To: 'Gary Thomas' Cc: eCos patches Subject: RE: Possible deadlock in serial.c Date: Wed, 21 May 2003 18:51:57 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-length: 522 > This looks reasonable to me and I have applied the change (patch > attached). Good :-) > I don't think that there will be any patches made to the 2.0 branch > now that it has been "released". Does that mean that the ecos-v2_0-branch will *not* be touched at all from now on? It comes as a surprise to me since I would expect bug-fixes with relevance for eCos 2.0 to be committed to this branch as well - thus only new features/major revisions would be kept solely in the latest branch. /David Marqvar Thrane & Thrane --=-OXp+k3MI92sNA8hpBFkB--