mirror of
https://github.com/martinvonz/jj.git
synced 2024-12-27 14:57:14 +00:00
c7ee24727a
I had tried to generate the protobuf code at build time many months ago, but decided against it because it slowed down the build too much. I didn't realize there was the "cargo:rerun-if-changed=<filename>" feature that time. Given that that exists, it seems like an obvious win to generate the source code at build time. I put the generated sources in `$OUT_DIR` (where [1] says they should be), then include them in the `protos` module by using the `include!` macro. The biggest problem with that is that I couldn't get IntelliJ to understand it, even after enabling the experimental features described in [2]. [1] https://doc.rust-lang.org/cargo/reference/build-script-examples.html#code-generation [2] https://github.com/intellij-rust/intellij-rust/issues/1908#issuecomment-592773865
36 lines
No EOL
907 B
Protocol Buffer
36 lines
No EOL
907 B
Protocol Buffer
// Copyright 2020 Google LLC
|
|
//
|
|
// Licensed under the Apache License, Version 2.0 (the "License");
|
|
// you may not use this file except in compliance with the License.
|
|
// You may obtain a copy of the License at
|
|
//
|
|
// https://www.apache.org/licenses/LICENSE-2.0
|
|
//
|
|
// Unless required by applicable law or agreed to in writing, software
|
|
// distributed under the License is distributed on an "AS IS" BASIS,
|
|
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
// See the License for the specific language governing permissions and
|
|
// limitations under the License.
|
|
|
|
syntax = "proto3";
|
|
|
|
enum FileType {
|
|
Normal = 0;
|
|
Symlink = 1;
|
|
Executable = 2;
|
|
}
|
|
|
|
message FileState {
|
|
uint64 mtime_millis_since_epoch = 1;
|
|
uint64 size = 2;
|
|
FileType file_type = 3;
|
|
}
|
|
|
|
message TreeState {
|
|
bytes tree_id = 1;
|
|
map<string, FileState> file_states = 2;
|
|
}
|
|
|
|
message Checkout {
|
|
bytes commit_id = 1;
|
|
} |