Downloadable Git bundle information for project python-git as of 2025-11-01 04:52:02 UTC:
| Project | Bundle (Downloadable git bundle) | Size | Expires (Time remaining before bundle may become unavailable) | Behind (Time since bundle creation until most recently received ref change) |
|---|---|---|---|---|
| python-git | python-git-d00af22c.bundle | 16.4 KiB | 3 days | current |
Download the python-git-d00af22c.bundle file using your favorite method.
Web browsers typically provide one-click pause and resume. The curl command line utility has a --continue-at option that can be used to resume an interrupted download.
Please note that it may not be possible to resume an interrupted download after the “Expires” time shown above so plan the bundle download accordingly.
Subsequent instructions will assume the downloaded bundle python-git-d00af22c.bundle is available in the current directory – adjust them if that’s not the case.
It is possible to use the git clone command to create a repository from a bundle file all in one step. However, that can result in unwanted local tracking branches being created, so we do not use git clone in this example.
This example creates a Git repository named “python-git” in the current directory, but that may be adjusted as desired:
git init python-git cd python-git git remote add origin ../python-git-d00af22c.bundle git fetch
Assuming the current directory is still set to the newly created “python-git” repository, we set the origin to a suitable fetch URL. Any valid fetch URL for the repository may be used instead of the one shown here:
git remote set-url origin https://repo.or.cz/python-git.git
Note that the python-git-d00af22c.bundle file is now no longer needed and may be kept or discarded as desired.
Assuming the current directory is still set to the newly created “python-git” repository, this example fetches the current HEAD symbolic ref (i.e. the branch that would be checked out by default if the repository had been cloned directly from a fetch URL instead of a bundle) and any changes made to the repository since the bundle was created:
git fetch --prune origin git remote set-head origin --auto
The amount retrieved by the fetch command depends on how many changes have been pushed to the repository since the bundle was created.
The set-head command will be very fast and may be omitted if one’s not interested in the repository’s default branch.
Assuming the current directory is still set to the newly created “python-git” repository, the list of available branches to checkout may be shown like so:
git branch -r
Note that if the repository has a default branch it will be shown in the listing preceded by “origin/HEAD -> ”.
In this case, however, the default branch is most likely “master” and may be checked out like so:
git checkout master
Note that the leading “origin/” was omitted from the branch name given to the git checkout command so that the automagic DWIM (Do What I Mean) logic kicks in.
The repository is now ready to be used just the same as though it had been cloned directly from a fetch URL.