An error occurred while fetching folder content.
Select Git revision
- Branches 13
- branch/future
- branch/default default
- topic/default/client-workdirs
- branch/oldstable
- branch/stable
- topic/default/rhgitaly-hg-call-root
- topic/default/example-client-sidecar
- topic/default/rhgitaly-phases
- topic/stable/hg-core-glob-regexp
- topic/stable/memleaks
- topic/default/repository-GetRawChanges
- topic/default/repo-cache
- topic/default/none-fast-paths
- Tags 142
- 0.1.0 protected
- 0.10.0 protected
- 0.11.0 protected
- 0.11.1 protected
- 0.11.2 protected
- 0.12.0 protected
- 0.12.1 protected
- 0.12.2 protected
- 0.13.0 protected
- 0.14.0 protected
- 0.14.1 protected
- 0.14.2 protected
- 0.14.3 protected
- 0.14.3-with-ruby protected
- 0.15.0 protected
- 0.16.0 protected
- 0.16.1 protected
- 0.17.0 protected
- 0.17.1 protected
- 0.18.0 protected
- 0.19.0 protected
- 0.2.0 protected
- 0.20.0 protected
- 0.21.0 protected
- 0.21.1 protected
- 0.22.0 protected
- 0.22.1 protected
- 0.22.2 protected
- 0.23.0 protected
- 0.24.0 protected
- 0.24.2 protected
- 0.24.3 protected
- 0.24.4 protected
- 0.25.0 protected
- 0.26.1 protected
- 0.26.2 protected
- 0.26.3 protected
- 0.27.0 protected
- 0.27.1 protected
- 0.27.2 protected
- 0.28.0 protected
- 0.29.0 protected
- 0.29.1 protected
- 0.3.0 protected
- 0.30.0 protected
- 0.31.0 protected
- 0.32.0 protected
- 0.32.1 protected
- 0.32.2 protected
- 0.33.0 protected
- 0.33.0dev0 protected
- 0.33.1 protected
- 0.33.2 protected
- 0.33.3 protected
- 0.33.4 protected
- 0.34.0 protected
- 0.35.0 protected
- 0.36.0 protected
- 0.37.0 protected
- 0.38.0 protected
- 0.39.0 protected
- 0.39.1 protected
- 0.4.0 protected
- 0.40.0 protected
- 0.40.1 protected
- 0.40.2 protected
- 0.40.3 protected
- 0.40.4 protected
- 0.41.0 protected
- 0.42.0 protected
- 0.42.1 protected
- 0.42.2 protected
- 0.42.3 protected
- 0.43.0 protected
- 0.43.1 protected
- 0.44.0 protected
- 0.44.1 protected
- 0.45.0 protected
- 0.5.0 protected
- 0.5.1 protected
- 0.6.0 protected
- 0.7.0 protected
- 0.7.1 protected
- 0.8.0 protected
- 0.8.1 protected
- 0.9.0 protected
- 1.0.0 protected
- 1.0.1 protected
- 1.1.0 protected
- 1.1.1 protected
- 1.1.2 protected
- 1.2.0 protected
- 1.3.0 protected
- 1.3.1 protected
- 1.3.2 protected
- 1.3.3 protected
- 1.3.4 protected
- 1.4.0 protected
- 1.4.1 protected
- 1.5.0 protected
- 1.6.0 protected
- 1.7.0 protected
- 1.7.1 protected
- 1.7.2 protected
- 17.10.0a0 protected
- 17.8.0 protected
- 17.8.1 protected
- 17.8.2 protected
- 17.8.3 protected
- 17.8.4 protected
- 17.9.0 protected
- 17.9.1 protected
- 2.0.0 protected
- 2.0.1 protected
- 2.0.2 protected
- 2.0.3 protected
- 2.1.0 protected
- 2.10.0 protected
- 2.11.0 protected
- 2.11.1 protected
- 2.2.0 protected
- 2.2.1 protected
- 2.2.2 protected
- 2.3.0 protected
- 2.3.1 protected
- 2.3.2 protected
- 2.3.3 protected
- 2.3.4 protected
- 2.4.0 protected
- 2.5.0 protected
- 2.5.1 protected
- 2.5.2 protected
- 2.5.3 protected
- 2.5.4 protected
- 2.5.5 protected
- 2.6.0 protected
- 2.7.0 protected
- 2.7.1 protected
- 2.7.2 protected
- 2.8.0 protected
- 2.8.1 protected
- 2.9.0 protected
Compare
-
-
- Open in your IDE
- Download source code
Georges Racinet
authored
This is partial because we don't have at the moment a clear way to get the commit responsible for the tag value, which would be needed to provide authorship and tag contents. In `mercurial.tags`, what is called `hist` is a list of previous tag *values*, hence is not what we need. Trying to reproduce the tag resolution logic, even with knowledge of the target changeset looks to be at best risky. Efficient extraction of that information would probably entail doing it along the target node information, and probably more caching.
16776923
History
Name | Last commit | Last update |
---|