mirror of
https://github.com/git-for-windows/git.git
synced 2026-06-27 13:21:17 -05:00
9759608622
The Git project is not exactly the easiest project to get started in: it's written in C and POSIX shell, with bits of Perl, Rust and other languages sprinkled into it. On top of that, the project has grown somewhat organically over time, making the codebase hard to navigate. These are problems that we're aware of, and there have been and still are efforts to clean up some of the technical debt that is natural to exist an a project that is more than 20 years old. Furthermore, we provide resources to newcomers that help them out like our coding guidelines, code of conduct or "MyFirstContribution.adoc". But there is a rather practical problem: finding your way around in our project's tree is not easy. Doing a directory listing in the top-level directory will present you with more than 550 files, which makes it extremely hard for a newcomer to figure out what files they are even supposed to look at. This makes the onboarding experience somewhat harder than it really needs to be. This isn't only a problem for newcomers though, as I myself struggle to find the files I am looking for because of the sheer number of files. Besides the problem of discoverability it also creates a problem of structure. It is not obvious at all which files are part of "libgit.a" and which files are only linked into our final executables. So while we have this split in our build systems, that split is not evident at all in our tree. Introduce a new "lib/" directory and move all of our sources for "libgit.a" into it to fix these issues. It makes the split we have evident and reduces the number of files in our top-level tree from 550 files to ~80 files. This is still a lot of files, but it's significantly easier to navigate already. Furthermore, we can further iterate after this step and think about introducing a better structure for remaining files, as well. Signed-off-by: Patrick Steinhardt <ps@pks.im> Signed-off-by: Junio C Hamano <gitster@pobox.com>
48 lines
1.6 KiB
C
48 lines
1.6 KiB
C
#ifndef SIDEBAND_H
|
|
#define SIDEBAND_H
|
|
|
|
enum sideband_type {
|
|
SIDEBAND_PROTOCOL_ERROR = -2,
|
|
SIDEBAND_REMOTE_ERROR = -1,
|
|
SIDEBAND_FLUSH = 0,
|
|
SIDEBAND_PRIMARY = 1
|
|
};
|
|
|
|
/*
|
|
* Inspects a multiplexed packet read from the remote. If this packet is a
|
|
* progress packet and thus should not be processed by the caller, returns 0.
|
|
* Otherwise, returns 1, releases scratch, and sets sideband_type.
|
|
*
|
|
* If this packet is SIDEBAND_PROTOCOL_ERROR, SIDEBAND_REMOTE_ERROR, or a
|
|
* progress packet, also prints a message to stderr.
|
|
*
|
|
* scratch must be a struct strbuf allocated by the caller. It is used to store
|
|
* progress messages split across multiple packets.
|
|
*
|
|
* The "status" parameter is a pkt-line response as returned by
|
|
* packet_read_with_status() (e.g., PACKET_READ_NORMAL).
|
|
*/
|
|
int demultiplex_sideband(const char *me, int status,
|
|
char *buf, int len,
|
|
int die_on_error,
|
|
struct strbuf *scratch,
|
|
enum sideband_type *sideband_type);
|
|
|
|
void send_sideband(int fd, int band, const char *data, ssize_t sz, int packet_max);
|
|
|
|
/*
|
|
* Apply sideband configuration for the given URL. This should be called
|
|
* when a transport is created to allow URL-specific configuration of
|
|
* sideband behavior (e.g., sideband.<url>.allowControlCharacters).
|
|
*/
|
|
void sideband_apply_url_config(const char *url);
|
|
|
|
/*
|
|
* Parse and set the sideband allow control characters configuration.
|
|
* The var parameter should be the key name (without section prefix).
|
|
* Returns 0 if the variable was recognized and handled, non-zero otherwise.
|
|
*/
|
|
int sideband_allow_control_characters_config(const char *var, const char *value);
|
|
|
|
#endif
|