From: "Isoken June Ibizugbe via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Isoken June Ibizugbe <isokenjune@gmail.com>
Subject: [PATCH 0/2] [Outreachy][PATCH v2] branch.c: adjust error messages to coding guidelines
Date: Fri, 13 Oct 2023 15:33:45 +0000 [thread overview]
Message-ID: <pull.1590.git.git.1697211227.gitgitgadget@gmail.com> (raw)
As per the CodingGuidelines document, it is recommended that a single-line
message provided to error messages such as die(), error() and warning(),
should start with a lowercase letter and should not end with a period.
Signed-off-by: Isoken June Ibizugbe isokenjune@gmail.com
Isoken June Ibizugbe (2):
branch.c: ammend error messages for die()
branch.c: adjust error messages to coding guidelines
builtin/branch.c | 66 ++++++++++++++++++++++++------------------------
1 file changed, 33 insertions(+), 33 deletions(-)
base-commit: aab89be2eb6ca51eefeb8c8066f673f447058856
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1590%2FJunie06%2Famend-error-mesg-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1590/Junie06/amend-error-mesg-v1
Pull-Request: https://github.com/git/git/pull/1590
--
gitgitgadget
next reply other threads:[~2023-10-13 15:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 15:33 Isoken June Ibizugbe via GitGitGadget [this message]
2023-10-13 15:33 ` [PATCH 1/2] branch.c: ammend error messages for die() Isoken June Ibizugbe via GitGitGadget
2023-10-13 15:33 ` [PATCH 2/2] branch.c: adjust error messages to coding guidelines Isoken June Ibizugbe via GitGitGadget
2023-10-13 15:40 ` Isoken Ibizugbe
2023-10-13 18:29 ` Junio C Hamano
2023-10-13 18:25 ` Rubén Justo
2023-10-13 18:30 ` [PATCH 0/2] [Outreachy][PATCH v2] " Rubén Justo
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=pull.1590.git.git.1697211227.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=isokenjune@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.