view hgweb.cgi @ 46814:c52c3c4cbd3f

copies: detect files as `touched/salvaged` if they only existed on one side

The file cannot be merged if there was content to merge on the other side. So
the previous record was wrong.

In the general case, the file existed only on one side and got touched during the
merge. So it should detected as touched.

They are a special case where the merge manually prevent the file to be deleted.
In this case the file is marked as `salvaged`.

The result of this `salvaged` recording, copy-tracing-wise, is the same as
recording it as `merged`. This is probably why they were recorded as `merged` in
the first place.

Differential Revision: https://phab.mercurial-scm.org/D10219

#!/usr/bin/env python3
#
# An example hgweb CGI script, edit as necessary
# See also https://mercurial-scm.org/wiki/PublishingRepositories

# Path to repo or hgweb config to serve (see 'hg help hgweb')
config = b"/path/to/repo/or/config"

# Uncomment and adjust if Mercurial is not installed system-wide
# (consult "installed modules" path from 'hg debuginstall'):
# import sys; sys.path.insert(0, "/path/to/python/lib")

# Uncomment to send python tracebacks to the browser if an error occurs:
# import cgitb; cgitb.enable()

from mercurial import demandimport

demandimport.enable()
from mercurial.hgweb import hgweb, wsgicgi

application = hgweb(config)
wsgicgi.launch(application)