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

packed-refs - write-through - apply creates/updates to packed-refs and optionally delete the original refs (purge) #139

Closed
Byron opened this issue Jul 28, 2021 · 0 comments
Closed

packed-refs - write-through - apply creates/updates to packed-refs and optionally delete the original refs (purge) #139

Byron opened this issue Jul 28, 2021 · 0 comments

Comments

@Byron
Copy link
Owner

Byron commented Jul 28, 2021

No description provided.

@Byron Byron mentioned this issue Jul 28, 2021
Open
7 tasks
Byron added a commit that referenced this issue Jul 28, 2021
@Byron
[ref #139] a complete test for the first packed-refs mode
f332dcf
Byron added a commit that referenced this issue Jul 28, 2021
@Byron
[ref #139] refactor
42215a1
Byron added a commit that referenced this issue Jul 28, 2021
@Byron
[ref #139] refactor
4e1b95e
Byron added a commit that referenced this issue Jul 28, 2021
@Byron
[ref #139] refactor
e5fbc4c
Byron added a commit that referenced this issue Jul 28, 2021
@Byron
[ref #139] Allow 'git pack-ref --no-purge' essentially
c32d8b7 
It's surprisingly easy to implement as well, neat.
Byron added a commit that referenced this issue Jul 28, 2021
@Byron
[ref #139] a first sketch to resolve object chains for packed ref pee…
54bc116 
…ling
Byron added a commit that referenced this issue Jul 28, 2021
@Byron
[ref #139] refactor
62558cb 
Reinvent the wheel less - after all we will need access to `git-object`
or delegate all chain following to the caller.

An alternative would be a feature-gated implementation of the resolution
algorithm behind behind function signature that doesn't know git-object,
but it's certainly not worth it.

Let's also think of revparsing, which definitely needs some git-object
access too.
@Byron Byron closed this as completed Jul 29, 2021
Byron added a commit that referenced this issue Jul 29, 2021
@Byron
[ref #139] a failing test for pruning loose refs into packed refs
437c610
Byron added a commit that referenced this issue Jul 29, 2021
@Byron
[ref #139] impl of loose ref deletion, but it doens't work yet…
f6631ad 
…primarily because the packed refs aren't actually created.
Byron added a commit that referenced this issue Jul 29, 2021
@Byron
[ref #139] Allow packed-refs creation in the presence of updates
0cf7314
Byron added a commit that referenced this issue Jul 29, 2021
@Byron
[ref #139] refactor
7e15817
Byron added a commit that referenced this issue Jul 29, 2021
@Byron
[ref #139] peeling for all refs to be written to a pack
cc891a1 
Even though we might want to filter this to only tags, we can't as
reference paths don't have to follow conventions. We just try to
peel tags and that's it, without even decoding the object.
Furthermore, tags are iterated to avoid any unnecessary work
there as well.
Byron added a commit that referenced this issue Jul 29, 2021
@Byron
[ref #139] refactor
a8f5d8d
Byron added a commit that referenced this issue Jul 29, 2021
@Byron
[ref #139] my first empty test but where else to document this :)?
0f00065
Byron added a commit that referenced this issue Jul 29, 2021
@Byron
[ref #139] add missing docs
5422ec8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Byron