In D8480#127657, @durin42 wrote:This patch is contentious, but I'm a little unclear why. Summarizing so everyone at least parses my thoughts roughly the way I mean: mandatory parts mean "fail if you can't process this part." It seems basically reasonable to me that a client can choose to ignore (perhaps through ignorance) obsolete markers and it'll be potentially confusing, but not /wrong/ in that they'll have the changesets they expected, but also didn't lose some the server thought they would. It feels like a bug if a client requests obsmarkers and then discards them?
Active Repositories
Active Repositories
- rHG Mercurial
- Mon, Jun 1, 9:22 AM
- Mercurial
- rNRWHG narrowhg
- 369 Commits
- ·
- Restricted Project
- Jan 26 2018, 6:48 PM
- Mercurial
Recent Activity
Recent Activity
Today
Today
marmoute updated the diff for D8587: metadata: move computation related to files touched in a dedicated module.
marmoute updated the diff for D8588: files: extract code for extra filtering of the `removed` entry into copies.
marmoute updated the diff for D8589: metadata: filter the `removed` set to only contains relevant data.
Yesterday
Yesterday
relnotes: advertize the possibility to use rust
rust: add a pointer for profiling to the README
valentin.gatienbaron committed rHG69d3ce00df99: rust: update the mention of hgcli in rust/README.rst.
rust: update the mention of hgcli in rust/README.rst
sslutil: fix comment to use inclusive or instead of exclusive or
mjacob committed rHG53b3baaadb64: sslutil: propagate return value ssl.PROTOCOL_SSLv23 from protocolsettings().
sslutil: propagate return value ssl.PROTOCOL_SSLv23 from protocolsettings()
mjacob committed rHG38e3df9ff1e7: sslutil: stop storing protocol and options for SSLContext in settings dict.
sslutil: stop storing protocol and options for SSLContext in settings dict
sslutil: rename 'minimumprotocolui' -> 'minimumprotocol'
mjacob committed rHG941fef7523c7: sslutil: remove dead code (that failed if only TLS 1.0 is available).
sslutil: remove dead code (that failed if only TLS 1.0 is available)
mjacob committed rHGd61c05450b37: sslutil: properly detect which TLS versions are supported by the ssl module.
sslutil: properly detect which TLS versions are supported by the ssl module
mjacob committed rHG5921dc0d5c3a: sslutil: remove dead code (that downgraded default minimum TLS version).
sslutil: remove dead code (that downgraded default minimum TLS version)
config: remove unused hostsecurity.disabletls10warning config
sslutil: remove comment referring to unsupported legacy stacks
setup: require that Python has TLS 1.1 or TLS 1.2
Sun, May 31
Sun, May 31
mjacob committed rHGabcd6db1f2cc: sslutil: don't set minimum TLS version to 1.0 if 1.2 but not 1.1 is available.
sslutil: don't set minimum TLS version to 1.0 if 1.2 but not 1.1 is available
sslutil: check for OpenSSL without TLS 1.0 support in one case
mjacob committed rHGceb7318013d5: sslutil: fix names of variables containing minimum protocol strings.
sslutil: fix names of variables containing minimum protocol strings
mjacob committed rHG4942c1bdd080: sslutil: add FIXME about supportedprotocols possibly containing too many items.
sslutil: add FIXME about supportedprotocols possibly containing too many items
mjacob committed rHG95903a8d8c97: sslutil: stop returning argument as third return value of protocolsettings().
sslutil: stop returning argument as third return value of protocolsettings()
mjacob committed rHG61cdc8137d53: relnotes: note that we now require modern SSL/TLS features in Python.
relnotes: note that we now require modern SSL/TLS features in Python
tests: stop checking for optional, now impossible output
Sat, May 30
Sat, May 30
Maybe another option is to allow multiple -d arguments for this case? Something like hg rebase -r C -d B -d D. I haven't thought through BC, but I think that's what I'd prefer if we were writing rebase from scratch. I know we can't support hg rebase -r C -d 'B + D' for backward-compatibility reasons (because we already support that -- it rebases to the highest revnum in the set).
Well, I attempted to rewrite @. But somehow the empty changeset got published before that push completed. So it is forever part of history now :/
It looks like hg phabread | hg import - produced an empty changeset, which I accidentally pushed. I have since rewritten @ on hg-committed to remove the empty changeset. This differential revision should be reopened (which I cannot do since I don't own it).
rust: remove one more occurrence of re2