Proto commits in scylladb/seastar

These 3 commits are when the Protocol Buffers files have changed:

2023-12-26

src/proto/metrics2.proto: newer proto buf definition Prometheus has updated its metrics2.proto definition. It is backward compatible but supports new options. This patch update the metrics2.proto file based on: https://raw.githubusercontent.com/prometheus/prometheus/release-2.44/prompb/io/prometheus/client/metrics.proto With the change of removing the gogoproto/gogo.proto support

The documentation is generated from this commit.

2018-11-20

Split private and public files It is important to differentiate public interface files and private implementation details. To that end, we move public headers to the `include` directory and move all source files and implementation-internal header files to the `src` directory. This change has the following benefits: - Clear separation between the public and private interface (check the location of the file). This can help with over-inclusion of headers and help to make future improvements in compilation time - It is easy to know which source files should be installed on the system (all files in the `include` directory) by build-systems or packaging tools There are (beneficial) side-effects: - All public header files now must be included with a prefix of "seastar", like #include <seastar/core/future.hh> instead of #include <core/future.hh> This is helpful for making it clear in client applications (or libraries) which header files belong to Seastar. - In the implementation of Seastar itself, all public header files are included with an absolute path relative to the `include` directory and with <>-delimiters, including those in the same directory. This eliminates ambiguity about the location of a header file and that it is public. - In the implementation of Seastar itself, all private header files are included with an absolute path relative to the `src` directory and with ""-delimiters, including those in the same directory. Like with public header files, this eliminates ambiguity about the location of the file on disk and also reinforces that the file is private. If these rules are adhered to, it will be highly unlikely (pending a naming conflict that would effectively need to be intentional) for a compilation to succeed if a public header file included a private one. However, private header and source files can include private and public header files.

2016-07-21

Import the metrics definition from prometheus This adds the prometheus proto file definition from the prometheus project. Signed-off-by: Amnon Heiman <amnon@scylladb.com>