https://gitlab.inria.fr/cado-nfs/cado-nfs
- HEAD
- refs/heads/1.0
- refs/heads/1.1
- refs/heads/2.0
- refs/heads/2.0.1
- refs/heads/2.1
- refs/heads/2.2
- refs/heads/2.3
- refs/heads/abhex
- refs/heads/bucket_sieve_powers
- refs/heads/chronograms
- refs/heads/ci-more-features
- refs/heads/client_wait
- refs/heads/codebase-dl
- refs/heads/coverity
- refs/heads/coverity-pre
- refs/heads/descent
- refs/heads/dist-alpha
- refs/heads/fb32
- refs/heads/fix-21825-c
- refs/heads/fullbatch
- refs/heads/future-new-merge
- refs/heads/hd
- refs/heads/investigate-30009
- refs/heads/investigate-30013
- refs/heads/master
- refs/heads/mnfs
- refs/heads/mod64
- refs/heads/nocomment_lognorm_murphy
- refs/heads/pp1_with_two_parameterizations
- refs/heads/reduce-plattice
- refs/heads/ropt_dev
- refs/heads/rsa220
- refs/heads/shrink-double
- refs/heads/simpler-merge
- refs/heads/simul
- refs/heads/smithcopper
- refs/heads/strategies
- refs/heads/use-relation-cache
- refs/merge-requests/11/head
- refs/merge-requests/11/merge
- refs/merge-requests/18/head
- refs/merge-requests/18/merge
- refs/merge-requests/23/head
- refs/merge-requests/23/merge
- refs/merge-requests/26/head
- refs/merge-requests/26/merge
- refs/merge-requests/27/head
- refs/merge-requests/27/merge
- refs/merge-requests/28/head
- refs/merge-requests/28/merge
- refs/merge-requests/29/head
- refs/merge-requests/29/merge
- refs/merge-requests/3/head
- refs/merge-requests/3/merge
- refs/merge-requests/30/head
- refs/merge-requests/30/merge
- refs/merge-requests/31/head
- refs/merge-requests/31/merge
- refs/merge-requests/32/head
- refs/merge-requests/32/merge
- refs/merge-requests/33/head
- refs/merge-requests/33/merge
- refs/merge-requests/34/head
- refs/merge-requests/34/merge
- refs/merge-requests/35/head
- refs/merge-requests/35/merge
- refs/merge-requests/36/head
- refs/merge-requests/36/merge
- refs/merge-requests/37/head
- refs/merge-requests/37/merge
- refs/merge-requests/38/head
- refs/merge-requests/38/merge
- refs/merge-requests/39/head
- refs/merge-requests/39/merge
- refs/merge-requests/40/head
- refs/merge-requests/40/merge
- refs/merge-requests/41/head
- refs/merge-requests/41/merge
- refs/merge-requests/42/head
- refs/merge-requests/42/merge
- refs/merge-requests/43/head
- refs/merge-requests/43/merge
- refs/merge-requests/44/head
- refs/merge-requests/44/merge
- refs/merge-requests/45/head
- refs/merge-requests/45/merge
- refs/merge-requests/46/head
- refs/merge-requests/47/head
- refs/merge-requests/47/merge
- refs/pipelines/215770
- refs/pipelines/215773
- refs/pipelines/215774
- refs/pipelines/215840
- refs/pipelines/215850
- refs/pipelines/215853
- refs/pipelines/215928
- refs/pipelines/215931
- refs/pipelines/235855
- refs/tags/1.1-RC1
- refs/tags/1.1-RC2
- refs/tags/1.1-RC3
- refs/tags/1.1-RC4
- refs/tags/1.1-RC5
- refs/tags/2.0-alpha1
- refs/tags/2.0-alpha2
- refs/tags/2.0-beta1
- refs/tags/2.2.0
- refs/tags/2.2.0-rc1
- refs/tags/2.3.0
- refs/tags/git-1.0
- refs/tags/git-1.1
- refs/tags/git-2.0
- refs/tags/git-2.0.1
- refs/tags/git-2.1
- refs/tags/git-2.1.1
- refs/tags/git-2.2.0
- refs/tags/git-2.3.0
Raw File
Take a new snapshot of a software origin
If the archived software origin currently browsed is not synchronized with its upstream version (for instance when new commits have been issued), you can explicitly request Software Heritage to take a new snapshot of it.
Use the form below to proceed. Once a request has been submitted and accepted, it will be processed as soon as possible. You can then check its processing state by visiting this dedicated page.Processing "take a new snapshot" request ...
Permalinks
To reference or cite the objects present in the Software Heritage archive, permalinks based on SoftWare Hash IDentifiers (SWHIDs) must be used.
Select below a type of object currently browsed in order to display its associated SWHID and permalink.
Tip revision: ae34c4dc61ca8e4bcfc15c322cf3f05f130d1d5d authored by Emmanuel Thomé on 19 April 2021, 12:01:44 UTC
Disable the fix of #30012. See !29 for a real fix.
Disable the fix of #30012. See !29 for a real fix.
Tip revision: ae34c4d
files.unknown
# This file lists files which don't go into the distribution. In contrast
# to files.nodist, this is not because one has decided not to distribute
# these files, but rather because it's undecided -- most likely because
# the committer forgot to add the information. So if ``make dist'' barfs,
# add a pattern to this file so that it eventually only prints a warning.
# The normal situation is to have an empty file here.