remove snapshot.proto comments
These comments don't really add any value as we can just view the next
enum value by looking at the struct. A lot of these are also outdated,
and require a second point of maintenance.
Bug: 332255580
Test: th
Change-Id: Ic235436b922ad51bd3b423d42e61c8c07c01690a
diff --git a/fs_mgr/libsnapshot/android/snapshot/snapshot.proto b/fs_mgr/libsnapshot/android/snapshot/snapshot.proto
index 36300de..8bd120d 100644
--- a/fs_mgr/libsnapshot/android/snapshot/snapshot.proto
+++ b/fs_mgr/libsnapshot/android/snapshot/snapshot.proto
@@ -17,7 +17,6 @@
option optimize_for = LITE_RUNTIME;
-// Next: 4
enum SnapshotState {
// No snapshot is found.
NONE = 0;
@@ -34,7 +33,6 @@
MERGE_COMPLETED = 3;
}
-// Next: 3
enum MergePhase {
// No merge is in progress.
NO_MERGE = 0;
@@ -46,7 +44,6 @@
SECOND_PHASE = 2;
}
-// Next: 13
message SnapshotStatus {
// Name of the snapshot. This is usually the name of the snapshotted
// logical partition; for example, "system_b".
@@ -131,7 +128,6 @@
reserved 20;
}
-// Next: 8
enum UpdateState {
// No update or merge is in progress.
None = 0;
@@ -160,7 +156,6 @@
Cancelled = 7;
};
-// Next 14:
//
// To understand the source of each failure, read snapshot.cpp. To handle new
// sources of failure, avoid reusing an existing code; add a new code instead.
@@ -188,7 +183,6 @@
WrongMergeCountConsistencyCheck = 20;
};
-// Next: 8
message SnapshotUpdateStatus {
UpdateState state = 1;
@@ -241,7 +235,6 @@
uint32 num_verification_threads = 16;
}
-// Next: 10
message SnapshotMergeReport {
// Status of the update after the merge attempts.
UpdateState state = 1;