This is the mail archive of the
mailing list for the glibc project.
Re: Need help in properly formatting a patch for glibc
- From: "Carlos O'Donell" <carlos at systemhalted dot org>
- To: "Denys Vlasenko" <dvlasenk at redhat dot com>
- Cc: "Ryan Arnold" <ryan dot arnold at gmail dot com>, libc-help at sourceware dot org
- Date: Tue, 19 Aug 2008 08:20:50 -0400
- Subject: Re: Need help in properly formatting a patch for glibc
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=H1zlQ4gUKeezZwh6qdxgntoua0W7+6I4FBi29TReeHI=; b=r39LPmNwFhyWbQ5LD1DDP3a57/HR8uGPdGOoMshJmPbnJWrAvs06Zw9U/4YlCLPdwk ZjWrlHfpIy9465LLUKJNlCaiVKdsu5iI7hqzlxM4SXKtiZEuDSzwlF33hhBgbyvgPU8L smnlQ9rxkMJSKquxw86Lq46WQBoGyEawRSaiw=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=DwfNI8QMDrQaEiHuV47JvrUKuPxBl/xohkPhdE/iX8dRLB9q6V6908/mlDGkcxatlb 6rlLGSRo2s3zL0wFaEVg/070TnAKc/nSmDYRQ1Ik2KM8FWO4eXiKC4SOHSHdPiOyEkZT oDMtrDsL2d+kCu1YgsN6Idj6IIKJ9zR7vxG5E=
- References: <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com>
On Tue, Aug 19, 2008 at 4:57 AM, Denys Vlasenko <firstname.lastname@example.org> wrote:
> On Mon, 2008-08-18 at 15:28 -0400, Carlos O'Donell wrote:
>> On Mon, Aug 18, 2008 at 11:42 AM, Ryan Arnold <email@example.com> wrote:
>> > On Mon, Aug 18, 2008 at 10:32 AM, Denys Vlasenko <firstname.lastname@example.org> wrote:
>> >> Please advice what I did wrong, and what is the correct Changelog
>> >> format.
>> Your patch also lacks the following:
>> 1. A detailed explanation of the patch.
>> e.g. Under what conditions does it occur?
> Details are at https://bugzilla.redhat.com/show_bug.cgi?id=457508
It is customary to repeat some of the important details *and* include
Please remember that we are all volunteers. You have to make it easy
for us to give you an "A+" on your bug report and patch.
Adding a summary of the relevant details helps give you an "A+"
>> 2. Testing.
>> e.g. After patching glibc, did you run the testsuite to verify your
>> patch didn't break anything?
> Yes, it does not break anything.
Excellent. It's important that you state something like "No
regressions on $target" where $target is the system on which you ran
the glibc testsuite. This shows the developers that you checked to see
if your patch caused regressions.