Skip to content
Permalink

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: alexcrichton/tar-rs
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 0.4.42
Choose a base ref
...
head repository: alexcrichton/tar-rs
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 0.4.43
Choose a head ref
  • 5 commits
  • 6 files changed
  • 3 contributors

Commits on Sep 26, 2024

  1. EntryWriter: Add comments for why ManuallyDrop is OK (#380)

    * EntryWriter: Add comments for why ManuallyDrop is OK
    
    This wasn't immediately obvious to me at least.
    xref: #376 (comment)
    
    Signed-off-by: Colin Walters <walters@verbum.org>
    Co-authored-by: xzfc <5121426+xzfc@users.noreply.github.com>
    cgwalters and xzfc authored Sep 26, 2024
    Copy the full SHA
    a1fd011 View commit details

Commits on Oct 24, 2024

  1. entry: Use our const for xattrs (#383)

    General code cleanup but the specific rationale here is I was
    trying to find the places this was used in the code and
    was surprising cross-referencing didn't turn up the unpacking code.
    
    Signed-off-by: Colin Walters <walters@verbum.org>
    cgwalters authored Oct 24, 2024
    Copy the full SHA
    9bd1372 View commit details
  2. tests: Just use unwrap() (#384)

    I don't think this unique-to-us `t!` macro is gaining anything
    really over just calling `unwrap()` directly which is *way*
    more widely used and idiomatic.
    
    I only converted a few testing functions to start momentum
    and hopefully new code can avoid `t!`.
    
    Signed-off-by: Colin Walters <walters@verbum.org>
    cgwalters authored Oct 24, 2024
    Copy the full SHA
    e0e69f6 View commit details
  3. Very basic Pax header writer (#382)

    * Implementation of a PAX header writer
    
    This crate currently supports reading the PAX headers. This adds a way to write
    some PAX headers in a Builder.
    Also implemented tests to showcase usage
    
    * Pax header handler, switch to not owned data types
    
    Since we can keep the ownership of the data when calling append_pax_extensions, we can use &str and &[u8] according to the lib documentation
    gwitrand-ovh authored Oct 24, 2024
    Copy the full SHA
    adbbc29 View commit details

Commits on Nov 1, 2024

  1. Release 0.4.43 (#386)

    The main feature in this release is a new API to write PAX
    extensions.
    cgwalters authored Nov 1, 2024
    Copy the full SHA
    2b1d374 View commit details
Loading