public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
Cc: isar-users@googlegroups.com, Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Re: [PATCH 1/1] fixed 2 typos in RECIPE-API-CHANGELOG.md (due to 87d31ee)
Date: Wed, 7 Dec 2022 11:32:10 +0300	[thread overview]
Message-ID: <71999837-9fac-9fe0-2d5e-f2f0e66aea86@ilbers.de> (raw)
In-Reply-To: <CAJGKYO6huw17DWK8fZLYd_dqCDiQTL-p1AnGRpwQJnodYabeYg@mail.gmail.com>

06.12.2022 23:52, Roberto A. Foglietta wrote:
> On Tue, 6 Dec 2022 at 20:56, Anton Mikanovich <amikan@ilbers.de> wrote:
>> I still see commit message "bugfix, typos, documentation" which do not looks
>> good enough. Also please mark updated patchsets as v2, v3, etc. next time.
>>
> Please check this patch, please. Thanks for your patience.
>
> Best regards, R-

Hello Roberto,

Thanks for improving submitting quality.
Just one note for the next time: marking patch/patchset version is 
usually done
in the '[PATCH]' prefix, like:

[PATCH v3] Fixed 2 typos in RECIPE-API-CHANGELOG.md

This can be done on patch generation stage in the following way:

git format-patch -v 3 HEAD~1

Or by --subject-prefix="PATCH v3" option of 'git send-email' command.


      reply	other threads:[~2022-12-07  8:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06 12:24 Roberto A. Foglietta
2022-12-06 13:30 ` Anton Mikanovich
2022-12-06 15:16   ` Roberto A. Foglietta
2022-12-06 19:56     ` Anton Mikanovich
2022-12-06 20:52       ` Roberto A. Foglietta
2022-12-07  8:32         ` Anton Mikanovich [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=71999837-9fac-9fe0-2d5e-f2f0e66aea86@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=ibr@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=roberto.foglietta@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox