Active Repositories
Active Repositories
- rHG Mercurial
- Fri, Jun 5, 1:20 AM
- Mercurial
- rNRWHG narrowhg
- 369 Commits
- ·
- Restricted Project
- Jan 26 2018, 6:48 PM
- Mercurial
Recent Activity
Recent Activity
Today
Today
mjacob committed rHG065704cbdbdb: py3: update comment to account for Python 2 and Python 3 differences.
py3: update comment to account for Python 2 and Python 3 differences
mjacob committed rHG7be784f301fa: py3: add warning about buffering behavior of pycompat.{stdout,stderr}.
py3: add warning about buffering behavior of pycompat.{stdout,stderr}
Yesterday
Yesterday
martinvonz retitled D8606: context: fix creation of ProgrammingError to not use non-existent field from context: fix creation of a ProgrammingError to not use non-existent field to context: fix creation of ProgrammingError to not use non-existent field.
mjacob added a comment to D8606: context: fix creation of ProgrammingError to not use non-existent field.
Otherwise, LGTM.
Wed, Jun 3
Wed, Jun 3
git: implement diff manifest method
git: add coverage for manifest.diff() so we don't regress
git: don't yield paths for directories when walking
git: properly visit child tree objects when resolving a path
git: correctly check for type of object when walking
git: implement stub prefetch_parents dirstate method
rust: leverage .expect() in place of .unwrap() + inline comment
rust: fix false comment about mpsc::Sender
Tue, Jun 2
Tue, Jun 2
graft: fix --base value to be saved in state file
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?
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.
Mon, Jun 1
Mon, Jun 1
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