From: Ronnie Sahlberg <sahlberg@google.com>
To: git@vger.kernel.org
Cc: Ronnie Sahlberg <sahlberg@google.com>
Subject: [PATCH v2 4/5] refs.c: make repack_without_refs static
Date: Wed, 30 Jul 2014 14:55:40 -0700 [thread overview]
Message-ID: <1406757341-4096-5-git-send-email-sahlberg@google.com> (raw)
In-Reply-To: <1406757341-4096-1-git-send-email-sahlberg@google.com>
Signed-off-by: Ronnie Sahlberg <sahlberg@google.com>
---
refs.c | 2 +-
refs.h | 3 ---
2 files changed, 1 insertion(+), 4 deletions(-)
diff --git a/refs.c b/refs.c
index bacce94..fc445e8 100644
--- a/refs.c
+++ b/refs.c
@@ -2538,7 +2538,7 @@ static int curate_packed_ref_fn(struct ref_entry *entry, void *cb_data)
/*
* Must be called with packed refs already locked (and sorted)
*/
-int repack_without_refs(const char **refnames, int n, struct strbuf *err)
+static int repack_without_refs(const char **refnames, int n, struct strbuf *err)
{
struct ref_dir *packed;
struct string_list refs_to_delete = STRING_LIST_INIT_DUP;
diff --git a/refs.h b/refs.h
index 23067a2..93f7bd5 100644
--- a/refs.h
+++ b/refs.h
@@ -155,9 +155,6 @@ extern void rollback_packed_refs(void);
*/
int pack_refs(unsigned int flags);
-extern int repack_without_refs(const char **refnames, int n,
- struct strbuf *err);
-
extern int ref_exists(const char *);
/*
--
2.0.1.523.g0041e8a
next prev parent reply other threads:[~2014-07-30 21:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 21:55 [PATCH v2 0/5] use packed refs for ref-transactions Ronnie Sahlberg
2014-07-30 21:55 ` [PATCH v2 1/5] refs.c: move reflog updates into its own function Ronnie Sahlberg
2014-07-30 21:55 ` [PATCH v2 2/5] refs.c: write updates to packed refs when a transaction has more than one ref Ronnie Sahlberg
2014-07-30 21:55 ` [PATCH v2 3/5] remote.c: use a transaction for deleting refs Ronnie Sahlberg
2014-07-30 21:55 ` Ronnie Sahlberg [this message]
2014-07-30 21:55 ` [PATCH v2 5/5] refs.c: make the *_packed_refs functions static Ronnie Sahlberg
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=1406757341-4096-5-git-send-email-sahlberg@google.com \
--to=sahlberg@google.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).