From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=65.50.211.136; helo=mail.zytor.com; envelope-from=pcacjr@zytor.com; receiver=edk2-devel@lists.01.org Received: from mail.zytor.com (terminus.zytor.com [65.50.211.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 474EA21F3882D for ; Fri, 13 Oct 2017 06:48:40 -0700 (PDT) Received: from [IPv6:2804:7f4:c480:c6be::2] ([IPv6:2804:7f4:c480:c6be:0:0:0:2]) (authenticated bits=0) by mail.zytor.com (8.15.2/8.15.2) with ESMTPSA id v9DDnpM7017750 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 13 Oct 2017 06:49:54 -0700 To: Laszlo Ersek , edk2-devel@lists.01.org Cc: Hao Wu , Ruiyu Ni , Eric Dong , Star Zeng References: <9ea64e48-25e1-f978-e1b1-c70a0b46e7dd@redhat.com> From: Paulo Alcantara Message-ID: <08b4ecc2-60a0-0480-c2cf-ba0b6d422461@zytor.com> Date: Fri, 13 Oct 2017 10:49:50 -0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <9ea64e48-25e1-f978-e1b1-c70a0b46e7dd@redhat.com> Subject: Re: [PATCH] MdeModulePkg/PartitionDxe: Fix UDF fs access on certain CD/DVD medias X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Oct 2017 13:48:40 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Hi Laszlo, On 13/10/2017 10:37, Laszlo Ersek wrote: > Hi Paulo, > > On 10/13/17 15:24, Paulo Alcantara wrote: >> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=725 > > Thank you for the patch. Some meta comments: > > When you post a patch for a TianoCore BZ, can you please > > (1) flip the TianoCore BZ in question to status IN_PROGRESS, > > (2) add a comment to the BZ, with a link to the patch in the mailing > list archive -- in this > case, the link would be: > > https://lists.01.org/pipermail/edk2-devel/2017-October/016031.html > > (3) optionally, assign the BZ to yourself? > > > In particular step (2) is very helpful when a BZ takes several > iterations of a patch set, and later someone would like to review the > evolution of the patches. > > (It's not necessary to comment at length in the BZ about the patch set > versions -- that's what the patch set cover letters are for --, > capturing the archive links is enough and helpful.) > > Finally, when the patch is applied and the BZ is fixed, it's best to: > > (4) kick the BZ to RESOLVED|FIXED, and > > (5) add a comment about the git commit hash of the patch. Sure. I'll make sure to follow those steps carefully next time. Thanks! I've just did (1), (2) and (3). Paulo