sapling/eden/scm/edenscm
Jun Wu 2d06b826c1 clone: log reasons we use legacy clone code path
Summary:
I found that there are still lots of (automation) users use the legacy clone
code path but it's unclear why (not having selectivepull?). Let's log the
reasons why the legacy path is used.

Reviewed By: sfilipco

Differential Revision: D27913616

fbshipit-source-id: b83f15e42a4afa94164b68bc9a91b4f0c022260c
2021-04-21 19:30:15 -07:00
..
hgdemandimport Back out "log: backout D24293498 about prefetching commit data" 2020-11-06 16:25:00 -08:00
hgext remotefilelog: move edenapi to localrepo 2021-04-21 19:30:15 -07:00
mercurial clone: log reasons we use legacy clone code path 2021-04-21 19:30:15 -07:00
__init__.py apply pyfmt with usort to opted-in sources 2020-11-10 21:25:54 -08:00
__main__.py edenscm: add a main module 2020-01-30 18:09:14 -08:00
hooks.py py3: fix conflictinfo compatibility 2020-09-01 18:31:35 -07:00
traceimport.py debugshell: improve "%trace" UX 2020-09-01 13:49:13 -07:00
tracing.py tracing: add isenabled 2021-04-21 09:25:49 -07:00