indygreg added a comment.
In https://phab.mercurial-scm.org/D2834#47334, @yuja wrote:
> Can we expect the BC of hgwebdir will be fixed before the release?
>
> I like the `/api/` namespace, but breaking existing hgweb instances
> wouldn't be acceptable.
yuja added a comment.
Can we expect the BC of hgwebdir will be fixed before the release?
I like the `/api/` namespace, but breaking existing hgweb instances
wouldn't be acceptable.
REPOSITORY
rHG Mercurial
REVISION DETAIL
https://phab.mercurial-scm.org/D2834
To: indygreg,
This revision was automatically updated to reflect the committed changes.
Closed by commit rHG1cfef5693203: wireproto: support /api/* URL space for
exposing APIs (authored by indygreg, committed by ).
REPOSITORY
rHG Mercurial
CHANGES SINCE LAST UPDATE
indygreg updated this revision to Diff 7194.
REPOSITORY
rHG Mercurial
CHANGES SINCE LAST UPDATE
https://phab.mercurial-scm.org/D2834?vs=7009=7194
REVISION DETAIL
https://phab.mercurial-scm.org/D2834
AFFECTED FILES
mercurial/configitems.py
mercurial/hgweb/hgweb_mod.py
indygreg added a comment.
So, assuming we can't introduce new top-level URLs without risking conflicts
with subrepos or hgwebdir virtual repos, for at least the wire protocol,
assuming we keep the `?cmd=capabilities` mechanism for the initial server
handshake, we can add something that
indygreg updated this revision to Diff 7009.
REPOSITORY
rHG Mercurial
CHANGES SINCE LAST UPDATE
https://phab.mercurial-scm.org/D2834?vs=6998=7009
REVISION DETAIL
https://phab.mercurial-scm.org/D2834
AFFECTED FILES
mercurial/configitems.py
mercurial/hgweb/hgweb_mod.py
indygreg updated this revision to Diff 6998.
REPOSITORY
rHG Mercurial
CHANGES SINCE LAST UPDATE
https://phab.mercurial-scm.org/D2834?vs=6979=6998
REVISION DETAIL
https://phab.mercurial-scm.org/D2834
AFFECTED FILES
mercurial/configitems.py
mercurial/hgweb/hgweb_mod.py
mharbison72 added a comment.
In https://phab.mercurial-scm.org/D2834#45696, @indygreg wrote:
> In https://phab.mercurial-scm.org/D2834#45666, @mharbison72 wrote:
>
> > Will this cause conflicts with `hg serve -S` or hgwebdir with
subrepo/virtual paths that start with 'api'? (This
indygreg added a comment.
In https://phab.mercurial-scm.org/D2834#45666, @mharbison72 wrote:
> Will this cause conflicts with `hg serve -S` or hgwebdir with
subrepo/virtual paths that start with 'api'? (This was the reason I used the
LFS URI starting with '.hg/', knowing that isn't
mharbison72 added a comment.
Will this cause conflicts with `hg serve -S` or hgwebdir with subrepo/virtual
paths that start with 'api'? (This was the reason I used the LFS URI starting
with '.hg/', knowing that isn't committable.)
REPOSITORY
rHG Mercurial
REVISION DETAIL
indygreg created this revision.
Herald added a subscriber: mercurial-devel.
Herald added a reviewer: hg-reviewers.
REVISION SUMMARY
I will soon be introducing a new version of the HTTP wire protocol.
One of the things I want to change with it is the URL routing.
I want to rely on URL paths
11 matches
Mail list logo
