Local clones and phases, mq (Re: [PATCH 1 of 5 phases] phases: exclude secret when doing a local clone)

Martin Geisler mg at lazybytes.net
Sun Jan 15 06:43:49 CST 2012


Matt Mackall <mpm at selenic.com> writes:

> On Fri, 2012-01-13 at 02:42 +0100, Pierre-Yves David wrote:
>> # HG changeset patch
>> # User Pierre-Yves David <pierre-yves.david at logilab.fr>
>> # Date 1326299187 -3600
>> # Node ID 3f56f39a5135f2253bdd8c14afe1e52a08b96ffc
>> # Parent  c47d69ce5208d5b5cfd2fb2f0f1d7a2b4795fbf5
>> phases: exclude secret when doing a local clone
>> 
>> This is achieved by denying copy clone when any secret changeset exist.

[...]

> So enforcing phases here means local clones are a) less useful b)
> slower and c) heavier than they could be.
>
> I'm honestly not sure what the right answer is here, and we can
> probably revisit this in the future.

I've also thought a bit about this problem and I prefer 'hg clone' to
copy everything, including secret changesets. Let people use the --pull
flag if they want a clone with what you've get over the wire.

-- 
Martin Geisler

Mercurial links: http://mercurial.ch/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20120115/740e784b/attachment.pgp>


More information about the Mercurial-devel mailing list