From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from us-smtp-delivery-1.mimecast.com (us-smtp-delivery-1.mimecast.com [207.211.31.81])
 by mx.groups.io with SMTP id smtpd.web10.19985.1592840121485974681
 for <devel@edk2.groups.io>;
 Mon, 22 Jun 2020 08:35:21 -0700
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=ghxDdjmU;
 spf=pass (domain: redhat.com, ip: 207.211.31.81, mailfrom: lersek@redhat.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
	s=mimecast20190719; t=1592840120;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:
	 in-reply-to:in-reply-to:references:references;
	bh=lmHio7tFrT4MuvhsSKy6M6jQ/UB//Hc97XHE92omhQM=;
	b=ghxDdjmUyHNBjj6gZH4KxFCksDO03PhwLPYTnxmRkhuCeSZoTDLlgLoG7G721N+c+nmMeW
	QlCV1HtswBgxpFtdibCBqXNJIu34pZJk5Hev9Zf598UyFXKWJmhfI3KSpFZgs05J/6Jfqv
	Sj+Yo/UrgKDmZ5fPxyJLg7iMUsKmgSo=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com
 [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id
 us-mta-183-Y-mod366Phu2lU52Q5kSmA-1; Mon, 22 Jun 2020 11:35:10 -0400
X-MC-Unique: Y-mod366Phu2lU52Q5kSmA-1
Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 43988464;
	Mon, 22 Jun 2020 15:35:09 +0000 (UTC)
Received: from lacos-laptop-7.usersys.redhat.com (ovpn-115-246.ams2.redhat.com [10.36.115.246])
	by smtp.corp.redhat.com (Postfix) with ESMTP id AA8E72B6D2;
	Mon, 22 Jun 2020 15:35:08 +0000 (UTC)
Subject: Re: [edk2-devel] EDK2 code standard question
To: devel@edk2.groups.io, hernan_gutierrez@hp.com
References: <CS1PR8401MB07288CD92DE102C180862B8A99980@CS1PR8401MB0728.NAMPRD84.PROD.OUTLOOK.COM>
From: "Laszlo Ersek" <lersek@redhat.com>
Message-ID: <0bdca40c-f4a3-f486-d125-d785d25ce9b4@redhat.com>
Date: Mon, 22 Jun 2020 17:35:07 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Firefox/52.0 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <CS1PR8401MB07288CD92DE102C180862B8A99980@CS1PR8401MB0728.NAMPRD84.PROD.OUTLOOK.COM>
X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Language: en-US
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit

On 06/19/20 19:25, Hernan via groups.io wrote:
> Hi,
> 
> I am a new to this group and I found something I think it is a problem in the documentation for code standards of edk2.
> Can you help me understand who/how I can request a revision on such detail in the documentation?
> 
> https://edk2-docs.gitbook.io/edk-ii-c-coding-standards-specification/5_source_files/57_c_programming
> 
> Section 5.7.1.10, specifically.

(1) Please register in the tianocore bugzilla at
<https://bugzilla.tianocore.org/>, and then file a new bug with the
following details:

- product: EDK2
- Component: documentation
- package: N/A
- Tianocore documents: EDK II C Coding Standards

In case you'd like to post patches too:

(2) You can clone the source repository for the document from:

- repo URL:
https://github.com/tianocore-docs/edk2-CCodingStandardsSpecification.git

- web UI:
https://github.com/tianocore-docs/edk2-CCodingStandardsSpecification

(3) Once you push your patches to your personal fork on github.com, you
can also sign up at <https://www.gitbook.com/>, and configure
integration with github.com. This will let you check a rendered view of
your changes before posting the patches. IIRC you can select, on
gitbook.com, the branch whose HEAD you'd like to render.

(4) For posting patches, please use the subject prefix "PATCH
edk2-CCodingStandardsSpecification" or "PATCH edk2-CCSS".

Thanks
Laszlo