- "message": "bpo-23404: make touch becomes make regen-all (#1466)\n\nDon't rebuild generated files based on file modification time\r\nanymore, the action is now explicit. Replace \"make touch\"\r\nwith \"make regen-all\".\r\n\r\nChanges:\r\n\r\n* Remove \"make touch\", Tools/hg/hgtouch.py and .hgtouch\r\n* Add a new \"make regen-all\" command to rebuild all generated files\r\n* Add subcommands to only generate specific files:\r\n\r\n - regen-ast: Include/Python-ast.h and Python/Python-ast.c\r\n - regen-grammar: Include/graminit.h and Python/graminit.c\r\n - regen-opcode-targets: Python/opcode_targets.h\r\n\r\n* Add PYTHON_FOR_REGEN variable\r\n* pgen is now only built by by \"make regen-grammar\"\r\n* Add $(srcdir)/ prefix to paths to source files to handle correctly\r\n compilation outside the source directory",
- "message": "Merge branch 'jc/am-i-v-fix'\n\nThe \"v(iew)\" subcommand of the interactive \"git am -i\" command was\nbroken in 2.6.0 timeframe when the command was rewritten in C.\n\n* jc/am-i-v-fix:\n am -i: fix \"v\"iew\n pager: factor out a helper to prepare a child process to run the pager\n pager: lose a separate argv[]\n",
<a href="https://docs.softwareheritage.org/devel/swh-model/apidoc/swh.model.html#swh.model.identifiers.directory_identifier">documentation</a> to get more details about how it is computed)
<a href="https://docs.softwareheritage.org/devel/swh-model/apidoc/swh.model.html#swh.model.identifiers.revision_identifier">documentation</a> to get more details about how it is computed)
<a href="https://docs.softwareheritage.org/devel/swh-model/apidoc/swh.model.html#swh.model.identifiers.snapshot_identifier">documentation</a> to get more details about how it is computed)
</li>
</ul>
<p>
Where hyperlinks are created when browsing these kind of endpoints, they always point to other context-independent browsing
URLs.
</p>
<h5>Context-dependent browsing</h5>
<p>
Context-dependent URLs provide information about objects, limited to specific contexts where the objects have been found.
</p>
<p>
Currently, browsing the Software Heritage objects in the context of an
<b>origin</b> is available. Below are some examples of such endpoints:
</p>
<ul>
<li>
Display information about the visits of a software
<h4 id="search-origins">Search software origins to browse</h4>
In order to facilitate the browsing of the archive and generate relevant entry points to it, a
<a href="{% url 'browse-search' %}">search interface</a> is available. Currently, it enables to search software origins from the URLs they were retrieved
from. More search criteria will be added in the future.
+ 'doc': 'information about the author of the revision'
+ },
+ {
+ 'name': 'author_url',
+ 'type': 'string',
+ 'doc': 'link to `</api/1/person/>`_ to get information about the author of the revision'
+ },
+ {
+ 'name': 'committer',
+ 'type': 'object',
+ 'doc': 'information about the committer of the revision'
+ },
+ {
+ 'name': 'committer_url',
+ 'type': 'string',
+ 'doc': 'link to `</api/1/person/>`_ to get information about the committer of the revision'
+ },
+ {
+ 'name': 'committer_date',
+ 'type': 'string',
+ 'doc': 'ISO representation of the commit date (in UTC)'
+ },
+ {
+ 'name': 'date',
+ 'type': 'string',
+ 'doc': 'ISO representation of the revision date (in UTC)'
+ },
+ {
+ 'name': 'directory',
+ 'type': 'string',
+ 'doc': 'the unique identifier that revision points to'
+ },
+ {
+ 'name': 'directory_url',
+ 'type': 'string',
+ 'doc': 'link to `</api/1/directory/>`_ to get information about the directory associated to the revision'
+ },
+ {
+ 'name': 'id',
+ 'type': 'string',
+ 'doc': 'the revision unique identifier'
+ },
+ {
+ 'name': 'merge',
+ 'type': 'boolean',
+ 'doc': 'whether or not the revision corresponds to a merge commit'
+ },
+ {
+ 'name': 'message',
+ 'type': 'string',
+ 'doc': 'the message associated to the revision'
+ },
+ {
+ 'name': 'parents',
+ 'type': 'array',
+ 'doc': 'the parents of the revision, i.e. the previous revisions that head directly to it, each entry of that array contains an unique parent revision identifier but also a link to `</api/1/revision/>`_ to get more informations about it'