From: john at keeping.me.uk (John Keeping)
Subject: [PATCH 2/4] shared: make cgit_free_taginfo() public
Date: Sat, 13 Aug 2016 12:04:30 +0100 [thread overview]
Message-ID: <8e353a45ccc8d4a09b9d348d517a2c896aaaac40.1471085819.git.john@keeping.me.uk> (raw)
In-Reply-To: <057c333e857a0fb1583cbeb68906df3ac80e18c4.1471085819.git.john@keeping.me.uk>
We will use this function from ui-tag.c in the next patch.
Signed-off-by: John Keeping <john at keeping.me.uk>
---
cgit.h | 1 +
shared.c | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/cgit.h b/cgit.h
index ec73dd3..c625161 100644
--- a/cgit.h
+++ b/cgit.h
@@ -344,6 +344,7 @@ extern int cgit_refs_cb(const char *refname, const struct object_id *oid,
int flags, void *cb_data);
extern void cgit_free_commitinfo(struct commitinfo *info);
+extern void cgit_free_taginfo(struct taginfo *info);
void cgit_diff_tree_cb(struct diff_queue_struct *q,
struct diff_options *options, void *data);
diff --git a/shared.c b/shared.c
index 432ce61..15ccecf 100644
--- a/shared.c
+++ b/shared.c
@@ -203,7 +203,7 @@ static struct refinfo *cgit_mk_refinfo(const char *refname, const struct object_
return ref;
}
-static void cgit_free_taginfo(struct taginfo *tag)
+void cgit_free_taginfo(struct taginfo *tag)
{
if (tag->tagger)
free(tag->tagger);
--
2.9.2.639.g855ae9f
next prev parent reply other threads:[~2016-08-13 11:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-13 11:04 [PATCH 1/4] shared: remove return value from cgit_free_commitinfo() john
2016-08-13 11:04 ` john [this message]
2016-08-13 11:04 ` [PATCH 3/4] ui-tag: clean up taginfo john
2016-08-13 11:04 ` [PATCH 4/4] ui-tree: remove a fixed size buffer john
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=8e353a45ccc8d4a09b9d348d517a2c896aaaac40.1471085819.git.john@keeping.me.uk \
--to=cgit@lists.zx2c4.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;
as well as URLs for NNTP newsgroup(s).