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.

Sign up for GitHub

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

Jump to bottom

Implement proper pack file negotiation with upload-pack #34

Open
j4yk opened this issue Apr 15, 2017 · 2 comments
Open

Implement proper pack file negotiation with upload-pack #34

j4yk opened this issue Apr 15, 2017 · 2 comments
Labels
bug FileSystem-Git help wanted Want pull requests because it is unlikely this will be worked on by the maintainers soon.

Comments

@j4yk
Copy link
Collaborator

j4yk commented Apr 15, 2017

Currently, done is sent immediately, hence a remote will always send the whole repository back as a packfile. Proper negotiation should be implemented to reduce traffic (and fetch time) as described in pack-protocol and http-protocol
@j4yk
Copy link
Collaborator Author

j4yk commented May 23, 2017

Fetching the whole repository all the time is particularly nasty if you have a large file in the repository at some point in the history...

@j4yk
Copy link
Collaborator Author

j4yk commented Oct 13, 2018

After this is resolved, we could optimize fetching by not unpacking the objects from the pack at all. The canonical Git just keeps the received pack file and creates an index for it.

@j4yk j4yk added the help wanted Want pull requests because it is unlikely this will be worked on by the maintainers soon. label Dec 8, 2019
@j4yk j4yk mentioned this issue Nov 8, 2021
Closed
@LinqLover LinqLover mentioned this issue Dec 28, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug FileSystem-Git help wanted Want pull requests because it is unlikely this will be worked on by the maintainers soon.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@j4yk