-
-
Notifications
You must be signed in to change notification settings - Fork 31
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: vbatts/tar-split
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.11.5
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: vbatts/tar-split
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v0.11.6
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 8 commits
- 7 files changed
- 3 contributors
Commits on Aug 26, 2023
-
Configuration menu - View commit details
-
Copy full SHA for bd00927 - Browse repository at this point
Copy the full SHA bd00927View commit details -
Configuration menu - View commit details
-
Copy full SHA for fe4605a - Browse repository at this point
Copy the full SHA fe4605aView commit details
Commits on Sep 11, 2024
-
This allows reading the metadata contained in tar-split without expensively recreating the whole tar stream including full contents. We have two use cases for this: - In a situation where tar-split is distributed along with a separate metadata stream, ensuring that the two are exactly consistent - Reading the tar headers allows making a ~cheap check of consistency of on-disk layers, just checking that the files exist in expected sizes, without reading the full contents. This can be implemented outside of this repo, but it's not ideal: - The function necessarily hard-codes some assumptions about how tar-split determines the boundaries of SegmentType/FileType entries (or, indeed, whether it uses FileType entries at all). That's best maintained directly beside the code that creates this. - The ExpectedPadding() value is not currently exported, so the consumer would have to heuristically guess where the padding ends. Signed-off-by: Miloslav Trmač <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 99c8914 - Browse repository at this point
Copy the full SHA 99c8914View commit details
Commits on Sep 26, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 93a41cf - Browse repository at this point
Copy the full SHA 93a41cfView commit details
Commits on Sep 27, 2024
-
github: drop go1.17, and add go1.21 & go1.22
Signed-off-by: Vincent Batts <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 84c1d45 - Browse repository at this point
Copy the full SHA 84c1d45View commit details -
Merge pull request #72 from vbatts/go-versions
github: drop go1.17, and add go1.21 & go1.22
Configuration menu - View commit details
-
Copy full SHA for ac25d96 - Browse repository at this point
Copy the full SHA ac25d96View commit details -
Configuration menu - View commit details
-
Copy full SHA for f39ca64 - Browse repository at this point
Copy the full SHA f39ca64View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1f44cc4 - Browse repository at this point
Copy the full SHA 1f44cc4View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v0.11.5...v0.11.6