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: NixOS/nix
base: fbcb897e21e6
Choose a base ref
...
head repository: NixOS/nix
compare: 38e360154d8e
Choose a head ref
  • 3 commits
  • 22 files changed
  • 1 contributor

Commits on Mar 17, 2020

  1. Copy the full SHA
    2a4e4f6 View commit details
    Browse the repository at this point in the history
  2. Require shallow clones to be requested explicitly

    If you do a fetchTree on a Git repository, whether the result contains
    a revCount attribute should not depend on whether that repository
    happens to be a shallow clone or not. That would complicate caching a
    lot and would be semantically messy. So applying fetchTree/fetchGit to
    a shallow repository is now an error unless you pass the attribute
    'shallow = true'. If 'shallow = true', we don't return revCount, even
    if the repository is not actually shallow.
    
    Note that Nix itself is not doing shallow clones at the moment. But it
    could do so as an optimisation if the user specifies 'shallow = true'.
    
    Issue #2988.
    edolstra committed Mar 17, 2020
    Copy the full SHA
    d1165d8 View commit details
    Browse the repository at this point in the history
  3. Copy the full SHA
    38e3601 View commit details
    Browse the repository at this point in the history