[PATCH] repoview: introduce "served-obsolete" filter for serving obsolete changesets

[Anton Shestakov]

On Fri, 15 Mar 2019 16:59:22 +0300
Pulkit Goyal <7895pulkit at gmail.com> wrote:

> On Tue, Mar 5, 2019 at 9:00 AM Anton Shestakov <av6 at dwimlabs.net> wrote:
> 
> > # HG changeset patch
> > # User Anton Shestakov <av6 at dwimlabs.net>
> > # Date 1551763152 -28800
> > #      Tue Mar 05 13:19:12 2019 +0800
> > # Node ID b6636687c713bf3c4b4c246b0e8759061d6e6742
> > # Parent  82d9728ace9535057d77df6c920385861ec00072
> > repoview: introduce "served-obsolete" filter for serving obsolete
> > changesets
> >
> > This filter allows viewing and pulling obsolete changesets (e.g. through
> > hgweb), but still doesn't allow secret commits to be seen. In other words,
> > this
> > is "served" plus obsolete commits, hence the name.
> >  
> 
> Is this also equivalent to (unfiltered-secret) commits?

Is "unfiltered-secret" an actual thing that exists? I couldn't find
anything with that name in hg. If it's a pseudo-revset, then yes,
"served-obsolete" is all changesets (unfiltered repo) minus secret
(that includes archived and internal).

"served-obsolete" is not "served" minus "obsolete", however: it's
served plus obsolete. I don't know if "served+obsolete" is a better
name, but test-obsolete.t passes with either of them.