How does"hg clone --depth" work?

[Jesus Cea]

On 12/11/20 11:04, Pierre-Yves David wrote:
> The --depth flag you are using is added by the narrow extension. An
> experimental extension from Google that requires server side support to
> be enabled). You probably do not want to rely on narrow.

So I have "--depth" because I have enabled "narrow" in the client, but
it doesn't work because I need client support?.

Do you have a reason to advice to not rely on narrow, beside being
marked as "experimental"?

> In what context are you trying to use --depth and which underlying issue
> are you trying to solve by using it ?

Simply hugely faster and smaller clones. The first could possibly be
solved with bundles, but needing to clone 372.144 changesets to solve a
typo seems a bit overkill...

Is it any other alternative, beside cloning the entire repository?

-- 
Jesús Cea Avión                         _/_/      _/_/_/        _/_/_/
jcea at jcea.es - https://www.jcea.es/    _/_/    _/_/  _/_/    _/_/  _/_/
Twitter: @jcea                        _/_/    _/_/          _/_/_/_/_/
jabber / xmpp:jcea at jabber.org  _/_/  _/_/    _/_/          _/_/  _/_/
"Things are not so easy"      _/_/  _/_/    _/_/  _/_/    _/_/  _/_/
"My name is Dump, Core Dump"   _/_/_/        _/_/_/      _/_/  _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20201113/1c144759/attachment.asc>