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.
https://phab.mercurial
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, #hg-revi
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
https://phab.mercurial-scm.org/D2834?vs=
indygreg updated this revision to Diff 7194.
REPOSITORY
rHG Mercurial
CHANGES SINCE LAST UPDATE
https://phab.mercurial-scm.org/D2834?vs=7009&id=7194
REVISION DETAIL
https://phab.mercurial-scm.org/D2834
AFFECTED FILES
mercurial/configitems.py
mercurial/hgweb/hgweb_mod.py
mercurial/wi
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 defin
indygreg updated this revision to Diff 7009.
REPOSITORY
rHG Mercurial
CHANGES SINCE LAST UPDATE
https://phab.mercurial-scm.org/D2834?vs=6998&id=7009
REVISION DETAIL
https://phab.mercurial-scm.org/D2834
AFFECTED FILES
mercurial/configitems.py
mercurial/hgweb/hgweb_mod.py
mercurial/wi
indygreg updated this revision to Diff 6998.
REPOSITORY
rHG Mercurial
CHANGES SINCE LAST UPDATE
https://phab.mercurial-scm.org/D2834?vs=6979&id=6998
REVISION DETAIL
https://phab.mercurial-scm.org/D2834
AFFECTED FILES
mercurial/configitems.py
mercurial/hgweb/hgweb_mod.py
mercurial/wi
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 was
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 comm
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
https://phab.m
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 t
11 matches
Mail list logo