From: Ramsay Jones <ramsay@ramsay1•demon.co.uk>
To: karthik.188@gmail•com
Cc: Junio C Hamano <gitster@pobox•com>,
Eric Sunshine <sunshine@sunshineco•com>,
GIT Mailing-list <git@vger•kernel.org>
Subject: [PATCH] sha1_file.c: make parse_sha1_header_extended() static
Date: Thu, 16 Apr 2015 13:25:25 +0100 [thread overview]
Message-ID: <552FAA35.4050806@ramsay1.demon.co.uk> (raw)
commit 9e1f5bc0 ("sha1_file.c: support reading from a loose object of
unknown type", 15-04-2015) added a new externally visible function
which does not require more than file scope. This causes sparse to
issue a warning message about this symbol. In order to suppress the
warning, add the static qualifier to the function definition.
[An alternative solution, if this symbol should have external scope,
is to add an external declaration for the function to the "cache.h"
header file (next to the one for parse_sha1_header()).]
Signed-off-by: Ramsay Jones <ramsay@ramsay1•demon.co.uk>
---
Hi Karthik,
If you need to re-roll your patches in the 'kn/cat-file-literally'
branch, could you please squash this, or something like it, into
the relevant patch.
Thanks!
ATB,
Ramsay Jones
sha1_file.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sha1_file.c b/sha1_file.c
index 267399d..2b81534 100644
--- a/sha1_file.c
+++ b/sha1_file.c
@@ -1642,7 +1642,7 @@ static void *unpack_sha1_rest(git_zstream *stream, void *buffer, unsigned long s
* too permissive for what we want to check. So do an anal
* object header parse by hand.
*/
-int parse_sha1_header_extended(const char *hdr, struct object_info *oi,
+static int parse_sha1_header_extended(const char *hdr, struct object_info *oi,
unsigned int flags)
{
struct strbuf typename = STRBUF_INIT;
--
2.3.0
next reply other threads:[~2015-04-16 12:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 12:25 Ramsay Jones [this message]
2015-04-17 2:03 ` [PATCH] sha1_file.c: make parse_sha1_header_extended() static Karthik Nayak
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=552FAA35.4050806@ramsay1.demon.co.uk \
--to=ramsay@ramsay1$(echo .)demon.co.uk \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=karthik.188@gmail$(echo .)com \
--cc=sunshine@sunshineco$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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