Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

NixOS / nix Public

Notifications You must be signed in to change notification settings
Fork 1.6k
Star 13.3k

Code
Issues 3.2k
Pull requests 379
Actions
Projects 2
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

Copy closure progress: Size tracking and a bug fix#6

Closed

shlevy wants to merge 4 commits intoNixOS:masterNixOS/nix:masterfrom shlevy:copy-closure-progressshlevy/nix:copy-closure-progressCopy head branch name to clipboard

+10-6

Conversation Commits4 (4)Checks Files changed

Commits

Commits on Apr 13, 2012

build-remote: CopyClosure::copyTo takes a new argument
shlevy
committed
nix-copy-closure: Have pv be size-aware when used
shlevy
committed
nix-copy-closure: Put the progressViewer after decompression always to avoid a delay between 'completion' according to pv and actual completion
shlevy
committed

Commits on Apr 17, 2012

nix-copy-closure: Don't hard-code the pv path when invoking remotely
shlevy
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.