git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Elia Pinto <gitter.spiros@gmail.com>
To: git@vger.kernel.org
Cc: Elia Pinto <gitter.spiros@gmail.com>
Subject: [PATCH 09/22] color.h: use the FORMATPRINTF macro to declare the gcc function attribute 'format printf'
Date: Thu, 11 Feb 2016 12:38:46 +0000	[thread overview]
Message-ID: <1455194339-859-10-git-send-email-gitter.spiros@gmail.com> (raw)
In-Reply-To: <1455194339-859-1-git-send-email-gitter.spiros@gmail.com>

Use the new FORMATPRINTF macro (in git-compat-util.h) to declare the gcc function
attribute 'format printf'

Signed-off-by: Elia Pinto <gitter.spiros@gmail.com>
---
 color.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/color.h b/color.h
index e155d13..8f763d7 100644
--- a/color.h
+++ b/color.h
@@ -86,9 +86,9 @@ int git_config_colorbool(const char *var, const char *value);
 int want_color(int var);
 int color_parse(const char *value, char *dst);
 int color_parse_mem(const char *value, int len, char *dst);
-__attribute__((format (printf, 3, 4)))
+FORMATPRINTF(3,4)
 int color_fprintf(FILE *fp, const char *color, const char *fmt, ...);
-__attribute__((format (printf, 3, 4)))
+FORMATPRINTF(3,4)
 int color_fprintf_ln(FILE *fp, const char *color, const char *fmt, ...);
 void color_print_strbuf(FILE *fp, const char *color, const struct strbuf *sb);
 
-- 
2.5.0

  parent reply	other threads:[~2016-02-11 12:40 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-11 12:38 [PATCH 00/22] add the FORMATPRINTF macro to declare the gcc function Elia Pinto
2016-02-11 12:38 ` [PATCH 01/22] git-compat-util.h: add the FORMATPRINTF macro Elia Pinto
2016-02-11 12:38 ` [PATCH 02/22] advice.h: use the FORMATPRINTF macro to declare the gcc function attribute 'format printf' Elia Pinto
2016-02-11 12:38 ` [PATCH 03/22] argv-array.h: " Elia Pinto
2016-02-11 20:53   ` Junio C Hamano
2016-02-11 21:49     ` Junio C Hamano
2016-02-11 12:38 ` [PATCH 04/22] builtin/index-pack.c: " Elia Pinto
2016-02-11 12:38 ` [PATCH 05/22] builtin/receive-pack.c: " Elia Pinto
2016-02-11 12:38 ` [PATCH 06/22] builtin/update-index.c: " Elia Pinto
2016-02-11 12:38 ` [PATCH 07/22] builtin/upload-archive.c: " Elia Pinto
2016-02-11 12:38 ` [PATCH 08/22] cache.h: " Elia Pinto
2016-02-11 12:38 ` Elia Pinto [this message]
2016-02-11 12:38 ` [PATCH 10/22] config.c: " Elia Pinto
2016-02-11 12:38 ` [PATCH 11/22] daemon.c: " Elia Pinto
2016-02-11 12:38 ` [PATCH 12/22] fsck.c: " Elia Pinto
2016-02-11 12:38 ` [PATCH 13/22] http-backend.c: " Elia Pinto
2016-02-11 12:38 ` [PATCH 14/22] imap-send.c: " Elia Pinto
2016-02-11 12:38 ` [PATCH 15/22] merge-recursive.c: " Elia Pinto
2016-02-11 12:38 ` [PATCH 16/22] pkt-line.h: " Elia Pinto
2016-02-11 12:38 ` [PATCH 17/22] remote.c: " Elia Pinto
2016-02-11 12:38 ` [PATCH 18/22] strbuf.h: " Elia Pinto
2016-02-11 12:38 ` [PATCH 19/22] trace.h: " Elia Pinto
2016-02-11 12:38 ` [PATCH 20/22] transport-helper.c: " Elia Pinto
2016-02-11 12:38 ` [PATCH 21/22] utf8.h: " Elia Pinto
2016-02-11 12:38 ` [PATCH 22/22] wt-status.h: " Elia Pinto
2016-02-11 17:59 ` [PATCH 00/22] add the FORMATPRINTF macro to declare the gcc function Junio C Hamano
2016-02-11 22:33   ` Jeff King
2016-02-18 21:59     ` Junio C Hamano

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=1455194339-859-10-git-send-email-gitter.spiros@gmail.com \
    --to=gitter.spiros@gmail.com \
    --cc=git@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).