From mint-bounce@lists.fishpool.fi Sun Aug 8 16:15:02 2010 Message-ID: <4C5F0FD6.6020301@freesbee.fr> Date: Sun, 08 Aug 2010 22:13:10 +0200 From: =?ISO-8859-1?Q?Vincent_Rivi=E8re?= User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: "mint@lists.fishpool.fi" Subject: Re: [MiNT] Rules for submitting patches References: <4C5F0A4A.6020004@online.no> In-Reply-To: <4C5F0A4A.6020004@online.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-Antivirus: avast! (VPS 100808-0, 08/08/2010), Outbound message X-Antivirus-Status: Clean X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: vincent.riviere@freesbee.fr Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id o78KF1xt011738 Jo Even Skarstein wrote: > "When fixing a bug or implementing a feature, it's important that you > don't change anything that's not directly related to this specific > change. If you do a lot of changes at once, it will be difficult for the > maintainers to evaluate your work." > >>From previous discussions I got the impression that the "rule" above is > correct when submitting patches, but apparently Mikro does not agree. > What's the maintainers' view on this? I think this rule is good and should be kept. -- Vincent Rivière