From: Ronnie Sahlberg <sahlberg@google.com>
To: git@vger.kernel.org
Cc: Ronnie Sahlberg <sahlberg@google.com>
Subject: [PATCH v3 11/16] refs.c: make repack_without_refs static
Date: Fri, 7 Nov 2014 11:39:00 -0800 [thread overview]
Message-ID: <1415389145-6391-12-git-send-email-sahlberg@google.com> (raw)
In-Reply-To: <1415389145-6391-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 c1db86f..2c6b0f6 100644
--- a/refs.c
+++ b/refs.c
@@ -2668,7 +2668,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(struct string_list *without, struct strbuf *err)
+static int repack_without_refs(struct string_list *without, 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 0ba078e..ce290b1 100644
--- a/refs.h
+++ b/refs.h
@@ -163,9 +163,6 @@ extern void rollback_packed_refs(void);
*/
int pack_refs(unsigned int flags);
-extern int repack_without_refs(struct string_list *without,
- struct strbuf *err);
-
extern int ref_exists(const char *);
extern int is_branch(const char *refname);
--
2.1.0.rc2.206.gedb03e5
next prev parent reply other threads:[~2014-11-07 19:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 19:38 [PATCH v3 00/16] ref-transaction-rename Ronnie Sahlberg
2014-11-07 19:38 ` [PATCH v3 01/16] refs.c: allow passing raw git_committer_info as email to _update_reflog Ronnie Sahlberg
2014-11-07 19:38 ` [PATCH v3 02/16] refs.c: return error instead of dying when locking fails during transaction Ronnie Sahlberg
2014-11-07 19:38 ` [PATCH v3 03/16] refs.c: use packed refs when deleting refs during a transaction Ronnie Sahlberg
2014-11-07 19:38 ` [PATCH v3 04/16] refs.c: use a stringlist for repack_without_refs Ronnie Sahlberg
2014-11-07 19:38 ` [PATCH v3 05/16] refs.c: add transaction support for renaming a reflog Ronnie Sahlberg
2014-11-07 19:38 ` [PATCH v3 06/16] refs.c: update rename_ref to use a transaction Ronnie Sahlberg
2014-11-07 19:38 ` [PATCH v3 07/16] refs.c: rollback the lockfile before we die() in repack_without_refs Ronnie Sahlberg
2014-11-07 19:38 ` [PATCH v3 08/16] refs.c: move reflog updates into its own function Ronnie Sahlberg
2014-11-07 19:38 ` [PATCH v3 09/16] refs.c: write updates to packed refs when a transaction has more than one ref Ronnie Sahlberg
2014-11-07 19:38 ` [PATCH v3 10/16] remote.c: use a transaction for deleting refs Ronnie Sahlberg
2014-11-07 19:39 ` Ronnie Sahlberg [this message]
2014-11-07 19:39 ` [PATCH v3 12/16] refs.c: make the *_packed_refs functions static Ronnie Sahlberg
2014-11-07 19:39 ` [PATCH v3 13/16] refs.c: replace the onerr argument in update_ref with a strbuf err Ronnie Sahlberg
2014-11-07 19:39 ` [PATCH v3 14/16] refs.c: make add_packed_ref return an error instead of calling die Ronnie Sahlberg
2014-11-07 19:39 ` [PATCH v3 15/16] refs.c: make lock_packed_refs take an err argument Ronnie Sahlberg
2014-11-07 19:39 ` [PATCH v3 16/16] refs.c: add an err argument to pack_refs 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=1415389145-6391-12-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).