Return-Path: virtio-comment-return-875-cohuck=redhat.com@lists.oasis-open.org Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 56B6A9860B2 for ; Thu, 24 Oct 2019 10:22:42 +0000 (UTC) From: Yoni Bettan Date: Thu, 24 Oct 2019 13:22:33 +0300 Message-Id: <20191024102234.41927-2-ybettan@redhat.com> In-Reply-To: <20191024102234.41927-1-ybettan@redhat.com> References: <20191024102234.41927-1-ybettan@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Subject: [virtio-comment] [PATCH 1/2] Rearranged the "Providing Feedback" section of README.md To: virtio-comment@lists.oasis-open.org Cc: Yoni Bettan , Yoni Bettan List-ID: From: Yoni Bettan Just arranged the alignment and also updated bullet #5 to fit multiple comm= its instead of a single one. Signed-off-by: Yoni Bettan --- README.md | 60 +++++++++++++++++++++++++++++++++++++------------------ 1 file changed, 41 insertions(+), 19 deletions(-) diff --git a/README.md b/README.md index 5ac84f9..f2fa5d0 100644 --- a/README.md +++ b/README.md @@ -71,25 +71,47 @@ have any attachments. A patch can be generated and sent by cloning the spec repository, creating a commit, formatting it as a patch and then sending it. For example: - -

-git clone https://github.com/oasis-tcs/virtio-spec.git
-... edit spec text, and save ...
-

-git commit -a
-... describe the proposed change, in the following format:
-single line summary
-
-detailed description, including motivation for the change
-
-Signed-off-by: Name <email>
-... then save and close the editor ...
-

-git format-patch -o proposal1/ HEAD~1..
-... generates a new directory proposal1/ and a file starting with 0001- ..= .
-

-git send-email --to=3Dvirtio-comment@lists.oasis-open.org proposal1/0001-* - +

    +
  1. + clone the repository using + git clone https://github.com/oasis-tcs/virtio-spec.git +
  2. + +
  3. + edit spec text and save
    +
  4. + +
  5. + commit changes using + git commit -a=20 + and describe the proposed change, in the following format:
    +
    + single line summary
    +
    + detailed description, including motivation for the change
    +
    + Signed-off-by: Name <email>
    +
    +
  6. + +
  7. + save and close the editor
    +
  8. + +
  9. + create the patch using=20 + + git format-patch -o proposal1/ HEAD~N + =20 + - it will generates a new directory 'proposal1/' and a files starting wi= th '0001-...' based on the last N commits of your git log
    + +
  10. + send the patch using=20 + + git send-email --to=3Dvirtio-comment@lists.oasis-open.org proposal1/00= 01-* + +
  11. +

Note for TC Members

TC Members should review TC specific process rules under "Further Description of this Repository" --=20 2.21.0 This publicly archived list offers a means to provide input to the=0D OASIS Virtual I/O Device (VIRTIO) TC.=0D =0D In order to verify user consent to the Feedback License terms and=0D to minimize spam in the list archive, subscription is required=0D before posting.=0D =0D Subscribe: virtio-comment-subscribe@lists.oasis-open.org=0D Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org=0D List help: virtio-comment-help@lists.oasis-open.org=0D List archive: https://lists.oasis-open.org/archives/virtio-comment/=0D Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf=0D List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists=0D Committee: https://www.oasis-open.org/committees/virtio/=0D Join OASIS: https://www.oasis-open.org/join/