From: Eric Wong <e@80x24.org>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Jeff King <peff@peff.net>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 2/1] server-info: conditionally update on fetch
Date: Wed, 15 May 2019 00:45:51 +0000 [thread overview]
Message-ID: <20190515004551.emrxvboqemwnqh4g@dcvr> (raw)
In-Reply-To: <87ftphw7mv.fsf@evledraar.gmail.com>
Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:
> Aside from this change, I wonder if making "fetch" optionally "exit 1"
> if no refs were updated would be useful, as in the below WIP. Of course
> it would be better to distinguish errors from "no refs to update".
Yes, we should've had this feature all along :)
And it's easy for me to build off your WIP to have fetch
update server info iff info/refs already exists:
-------8<-------
Subject: [PATCH 2/1] server-info: conditionally update on fetch
Since fetch can invalidate existing server info files, use the
new `updated_refs' counter to update server info files iff
info/refs already exists.
Note: this depends on Ævar's WIP in:
https://public-inbox.org/git/87ftphw7mv.fsf@evledraar.gmail.com/
Signed-off-by: Eric Wong <e@80x24.org>
---
builtin/fetch.c | 3 +++
server-info.c | 22 +++++++++++++++++++---
t/t5513-fetch-track.sh | 21 +++++++++++++++++++++
3 files changed, 43 insertions(+), 3 deletions(-)
diff --git a/builtin/fetch.c b/builtin/fetch.c
index da5414d9db..b35d4d105d 100644
--- a/builtin/fetch.c
+++ b/builtin/fetch.c
@@ -1681,6 +1681,9 @@ int cmd_fetch(int argc, const char **argv, const char *prefix)
close_all_packs(the_repository->objects);
+ if (updated_refs)
+ update_server_info(-1);
+
argv_array_pushl(&argv_gc_auto, "gc", "--auto", NULL);
if (verbosity < 0)
argv_array_push(&argv_gc_auto, "--quiet");
diff --git a/server-info.c b/server-info.c
index e68f785c2f..d4065d56a3 100644
--- a/server-info.c
+++ b/server-info.c
@@ -7,6 +7,7 @@
#include "packfile.h"
#include "object-store.h"
#include "strbuf.h"
+#include "dir.h"
struct update_info_ctx {
FILE *cur_fp;
@@ -170,10 +171,25 @@ static int generate_info_refs(struct update_info_ctx *uic)
return for_each_ref(add_info_ref, uic);
}
-static int update_info_refs(int force)
+static int want_update(int *force, const char *path)
+{
+ if (*force < 0) {
+ if (file_exists(path))
+ *force = 0; /* continue to normal update */
+ else
+ return 0;
+ }
+ return 1;
+}
+
+static int update_info_refs(int *force)
{
char *path = git_pathdup("info/refs");
- int ret = update_info_file(path, generate_info_refs, force);
+ int ret = 0;
+
+ if (want_update(force, path))
+ ret = update_info_file(path, generate_info_refs, *force);
+
free(path);
return ret;
}
@@ -361,7 +377,7 @@ int update_server_info(int force)
*/
int errs = 0;
- errs = errs | update_info_refs(force);
+ errs = errs | update_info_refs(&force);
errs = errs | update_info_packs(force);
/* remove leftover rev-cache file if there is any */
diff --git a/t/t5513-fetch-track.sh b/t/t5513-fetch-track.sh
index 65d1e05bd6..421f16ddfd 100755
--- a/t/t5513-fetch-track.sh
+++ b/t/t5513-fetch-track.sh
@@ -27,4 +27,25 @@ test_expect_success fetch '
)
'
+test_expect_success 'info/refs not created by fetch' '
+ (
+ cd other &&
+ test_path_is_dir .git/info &&
+ ! test_path_is_file .git/info/refs
+ )
+'
+
+test_expect_success 'info/refs updated by fetch if it already exists' '
+ git branch b/for-info-refs &&
+ (
+ cd other &&
+ git update-server-info &&
+ test_path_is_file .git/info/refs &&
+ ! grep b/for-info-refs .git/info/refs &&
+ git fetch &&
+ test_path_is_file .git/info/refs &&
+ grep b/for-info-refs .git/info/refs
+ )
+'
+
test_done
--
EW
next prev parent reply other threads:[~2019-05-15 0:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-11 1:34 [PATCH] update-server-info: avoid needless overwrites Eric Wong
2019-05-11 7:35 ` Eric Sunshine
2019-05-11 20:47 ` [PATCH v2] " Eric Wong
2019-05-11 21:17 ` [PATCH] " Eric Wong
2019-05-11 23:37 ` Ævar Arnfjörð Bjarmason
2019-05-12 0:38 ` Eric Wong
2019-05-12 4:08 ` Jeff King
2019-05-12 7:16 ` Ævar Arnfjörð Bjarmason
2019-05-14 9:47 ` Jeff King
2019-05-14 10:33 ` Ævar Arnfjörð Bjarmason
2019-05-14 11:24 ` Jeff King
2019-05-14 11:57 ` Ævar Arnfjörð Bjarmason
2019-05-14 11:50 ` Eric Wong
2019-05-14 12:13 ` dumb HTTP things I want to do Eric Wong
2019-05-14 12:27 ` Jeff King
2019-05-14 12:19 ` [PATCH] update-server-info: avoid needless overwrites Ævar Arnfjörð Bjarmason
2019-05-14 12:29 ` Jeff King
2019-05-15 0:45 ` Eric Wong [this message]
2019-05-15 20:38 ` [WIP] repack leaving stale entries in objects/info/packs Eric Wong
2019-05-15 21:48 ` Jeff King
2019-05-23 8:59 ` [PATCH] server-info: do not list unlinked packs Eric Wong
2019-05-23 10:24 ` Jeff King
2019-05-23 17:27 ` [PATCH v2] " Eric Wong
2019-05-24 6:05 ` Jeff King
2019-05-24 7:34 ` Ævar Arnfjörð Bjarmason
2019-05-13 23:17 ` [PATCH v3] update-server-info: avoid needless overwrites Eric Wong
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190515004551.emrxvboqemwnqh4g@dcvr \
--to=e@80x24.org \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).