Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitaly.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPatrick Steinhardt <psteinhardt@gitlab.com>2022-07-22 12:34:39 +0300
committerPatrick Steinhardt <psteinhardt@gitlab.com>2022-07-27 16:14:05 +0300
commitf6114dab48951ac98469da02769c04a9c9125f89 (patch)
tree127b79282bec17a982e5429a960eeb264a6c57ff /ruby/proto
parent5e7c8bbf1629203078b56ea98de87bc34dc037cf (diff)
proto: Remove unused `Repack` field from FetchIntoObjectPoolRequest
The `FetchIntoObjectPoolRequest` messages has a `Repack` field that supposedly controls whether the repository should or should not be repacked. This flag is completely ignored though and has always been ignored. It also isn't ever set by the Rails client. Remove the field without replacement for the time being. It seems like there is no usecase for it right now and it's bad to keep a no-op flag around in our code. Furthermore, we will want to fully move repository housekeeping into Gitaly eventually anyway.
Diffstat (limited to 'ruby/proto')
-rw-r--r--ruby/proto/gitaly/objectpool_pb.rb1
1 files changed, 0 insertions, 1 deletions
diff --git a/ruby/proto/gitaly/objectpool_pb.rb b/ruby/proto/gitaly/objectpool_pb.rb
index ebbe7fa8f..f022a19d6 100644
--- a/ruby/proto/gitaly/objectpool_pb.rb
+++ b/ruby/proto/gitaly/objectpool_pb.rb
@@ -37,7 +37,6 @@ Google::Protobuf::DescriptorPool.generated_pool.build do
add_message "gitaly.FetchIntoObjectPoolRequest" do
optional :origin, :message, 1, "gitaly.Repository"
optional :object_pool, :message, 2, "gitaly.ObjectPool"
- optional :repack, :bool, 3
end
add_message "gitaly.FetchIntoObjectPoolResponse" do
end