[docs] bug/patch handling checklist (Fwd: [d-kernel] [Fwd: Re: [Unionfs] Xattrs status])

[Michael Shigorin]

----- Forwarded message from Anton Farygin <rider altlinux.com> -----

Date: Tue, 08 Feb 2005 09:09:07 +0300
From: Anton Farygin <rider altlinux.com>
To: ALT Linux kernel packages development <devel-kernel altlinux.ru>
Subject: [d-kernel] [Fwd: Re: [Unionfs] Xattrs status]

Могу сказать, что перечисленные правила создания отчета об ошибке
весьма правильные ;-)

Rgds,
Rider


Date: Mon, 07 Feb 2005 09:23:10 -0500
From: "Charles P. Wright" <cwright cs.sunysb.edu>
To: jsingh ensim.com
Subject: Re: [Unionfs] Xattrs status
Cc: Unionfs <unionfs filesystems.org>, Dave Quigley <dquigley ic.sunysb.edu>

[skip]

Here are a few guidelines for these types of bugfixes:
1. Report one bug, or N very closely related bugs, at a time (in
bugzilla)
2. Include a small testcase that did not work before, preferably using
standard tools, but does work now.  Include your expected results, and
actual results.
3. Include a patch to fix that one bug.  This is related to part one, it
is easier to review one fix at a time for correctness, etc. rather than
having a large segment of code to look at before deciding whether to
accept or reject the patch.

Thanks,
Charles

----- End forwarded message -----

-- 
 ---- WBR, Michael Shigorin <mike на altlinux.ru>
  ------ Linux.Kiev http://www.linux.kiev.ua/