From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Bruno Albuquerque" <bga@google.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: [PATCH] protocol-caps.h: add newline at end of file
Date: Mon, 7 Jun 2021 16:33:05 +0200 [thread overview]
Message-ID: <patch-1.1-2302c9d522-20210607T143157Z-avarab@gmail.com> (raw)
In-Reply-To: <20210420233830.2181153-1-bga@google.com>
Add a trailing newline to the protocol-caps.h file added in the recent
a2ba162cda (object-info: support for retrieving object info,
2021-04-20). Various editors add this implicitly, and some compilers
warn about the lack of a \n here.
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
---
protocol-caps.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/protocol-caps.h b/protocol-caps.h
index 6351648e37..0a9f49df11 100644
--- a/protocol-caps.h
+++ b/protocol-caps.h
@@ -7,4 +7,4 @@ struct packet_reader;
int cap_object_info(struct repository *r, struct strvec *keys,
struct packet_reader *request);
-#endif /* PROTOCOL_CAPS_H */
\ No newline at end of file
+#endif /* PROTOCOL_CAPS_H */
--
2.32.0.rc3.434.gd8aed1f08a7
next prev parent reply other threads:[~2021-06-07 14:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 23:38 [PATCH v2] object-info: support for retrieving object info Bruno Albuquerque
2021-04-21 0:42 ` Junio C Hamano
2021-04-30 5:45 ` Junio C Hamano
2021-06-07 14:33 ` Ævar Arnfjörð Bjarmason [this message]
2021-06-09 17:20 ` [PATCH] protocol-caps.h: add newline at end of file Bruno Albuquerque
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=patch-1.1-2302c9d522-20210607T143157Z-avarab@gmail.com \
--to=avarab@gmail.com \
--cc=bga@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).