From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 1/4] v2writable: split off unindex_range mapping
Date: Thu, 30 May 2019 06:52:24 +0000 [thread overview]
Message-ID: <20190530065227.17641-2-e@80x24.org> (raw)
In-Reply-To: <20190530065227.17641-1-e@80x24.org>
It'll make it easier to detect if we have anything to
unindex and run git-log on, at all.
---
lib/PublicInbox/V2Writable.pm | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/lib/PublicInbox/V2Writable.pm b/lib/PublicInbox/V2Writable.pm
index 6b01171..df8cfb4 100644
--- a/lib/PublicInbox/V2Writable.pm
+++ b/lib/PublicInbox/V2Writable.pm
@@ -861,7 +861,7 @@ Rewritten history? (in $git->{git_dir})
reindexing $git->{git_dir} starting at
$range
- $sync->{"unindex-range.$i"} = "$base..$cur";
+ $sync->{unindex_range}->{$i} = "$base..$cur";
}
$range;
}
@@ -993,6 +993,7 @@ sub index_sync {
my $sync = {
mm_tmp => $self->{mm}->tmp_clone,
D => {}, # "$mid\0$cid" => $oid
+ unindex_range => {}, # EPOCH => oid_old..oid_new
reindex => $opt->{reindex},
-opt => $opt
};
@@ -1009,7 +1010,7 @@ sub index_sync {
-d $git_dir or next; # missing parts are fine
fill_alternates($self, $i);
my $git = PublicInbox::Git->new($git_dir);
- my $unindex_range = delete $sync->{"unindex-range.$i"};
+ my $unindex_range = delete $sync->{unindex_range}->{$i};
unindex($self, $sync, $git, $unindex_range) if $unindex_range;
defined(my $range = $sync->{ranges}->[$i]) or next;
$pr->("$i.git indexing $range\n") if $pr;
--
EW
next prev parent reply other threads:[~2019-05-30 6:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 6:52 [PATCH 0/4] v2writable: speedup no-op -index invocation Eric Wong
2019-05-30 6:52 ` Eric Wong [this message]
2019-05-30 6:52 ` [PATCH 2/4] v2writable: hoist out index_epoch sub Eric Wong
2019-05-30 6:52 ` [PATCH 3/4] v2writable: avoid mm_tmp creation without regen Eric Wong
2019-05-30 6:52 ` [PATCH 4/4] v2writable: short-circuit is_ancestor check on equality 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: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190530065227.17641-2-e@80x24.org \
--to=e@80x24.org \
--cc=meta@public-inbox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.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).