Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To: cygwin-apps AT cygwin DOT com
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
From: "Ralf Habacker" <Ralf DOT Habacker AT freenet DOT de>
To: <cygwin-apps AT cygwin DOT com>
Subject: RE: question about objdump output format ?
Date: Tue, 28 May 2002 21:18:39 +0200
Message-ID: <005401c2067c$78fd1b00$651c440a@BRAMSCHE>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
Importance: Normal
In-Reply-To: <20020528174402.GA2897@redhat.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400

> Regardless, basic patch management would dictate that you provide
> patches against plain CVS.  You shouldn't expect maintainers to apply
> unrelated patches in order to check your changes in.
>
... but the segfault patch is pending and the removing duplicate line patch
makes no sense (in true it does not work) without th segfault patches. So what
should I do ?
The is a possibility, I can merge both patches and submit it as one, but this
infringe a rule, that patches should cover only single issues because of easier
testing, isn't it ?

So should I merge the patches or what should I do ?

Regards
Ralf