Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for Git v2 protocol #371

Open
j4yk opened this issue Feb 21, 2022 · 0 comments
Open

Add support for Git v2 protocol #371

j4yk opened this issue Feb 21, 2022 · 0 comments
Labels
enhancement FileSystem-Git help wanted Want pull requests because it is unlikely this will be worked on by the maintainers soon. mandatory

Comments

@j4yk
Copy link
Collaborator

j4yk commented Feb 21, 2022

https://github.com/git/git/blob/v2.39.2/Documentation/gitprotocol-v2.txt

Among other things it allows to get a filtered list of refs from the server. This would allow for repositories with massive amounts of branches or tags, which in turn would allow for more "creative" uses of Git for Smalltalk. For example, tag each commit with a Monticello version name, have each package on its own branch to get per-package history, and overall create a more fitting Git storage backend for the Monticello versioning model (if desired). Since commercial Smalltalk version control systems like ENVY and Store tend to be more similar to Monticello than to "vanilla" Git, an approximation of those with a Git backend would also benefit from this approach.

Eventually (after a few years) this may be required to talk to certain services like GitHub. Hence tagged as mandatory.

@j4yk j4yk added enhancement help wanted Want pull requests because it is unlikely this will be worked on by the maintainers soon. mandatory FileSystem-Git labels Feb 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement FileSystem-Git help wanted Want pull requests because it is unlikely this will be worked on by the maintainers soon. mandatory
Projects
None yet
Development

No branches or pull requests

1 participant