[PATCH 2 of 3 V2] repoview: introduce a `experimental.extra-filter-revs` config
Pierre-Yves David
pierre-yves.david at ens-lyon.org
Wed Apr 17 09:47:54 EDT 2019
On 4/17/19 3:44 PM, Martin von Zweigbergk wrote:
>
>
> On Wed, Apr 17, 2019, 06:42 Martin von Zweigbergk <martinvonz at google.com
> <mailto:martinvonz at google.com>> wrote:
>
>
>
> On Tue, Apr 16, 2019, 11:52 Pierre-Yves David
> <pierre-yves.david at ens-lyon.org
> <mailto:pierre-yves.david at ens-lyon.org>> wrote:
>
> # HG changeset patch
> # User Pierre-Yves David <pierre-yves.david at octobus.net
> <mailto:pierre-yves.david at octobus.net>>
> # Date 1554565579 -7200
> # Sat Apr 06 17:46:19 2019 +0200
> # Node ID 898753ab5830bed2a7e16639a746376fa447577f
> # Parent 56e2557a9401a3b3c60956b86860c84fb2e1330a
> # EXP-Topic repoview
> # Available At https://bitbucket.org/octobus/mercurial-devel/
> # hg pull
> https://bitbucket.org/octobus/mercurial-devel/ -r 898753ab5830
> repoview: introduce a `experimental.extra-filter-revs` config
>
> The option define revisions to additionally filter out of all
> repository "view".
> The end goal is to provide and easy to way to serve multiple
> subset of the same
> repository using multiple "shares".
>
> The simplest use case of this feature is to have one view
> serving the public
> changesets and one view also serving the draft. This is
> currently achievable
> using the new `server.view` option introduced recently by Joerg
> Sonnenberger.
>
>
> Does that mean your mechanism can replace server.view? Do you plan
> to remove that feature? I haven't checked, but it would be nice to
> mark it experimental in 5.0 if it's not too late if we won't need it
> after this feature is done.
>
>
> ... and I just saw that your commit that does just that went public. Thanks!
<shelving my time travel helmet>
You are welcome.
--
Pierre-Yves David
More information about the Mercurial-devel
mailing list