[PATCH 3 of 3 STABLE] clone: copy obsolete marker on local clone

[Adrian Buehlmann]

On 2012-07-19 21:19, Pierre-Yves David wrote:
> # HG changeset patch
> # User Pierre-Yves.David at ens-lyon.org
> # Date 1342725079 -7200
> # Branch stable
> # Node ID d28fd79efcfd49272b3fbb45634a0cb7835a5b7c
> # Parent  ca58a884607433c52d2ba41ec63f8c1d43c0952e
> clone: copy obsolete marker on local clone
                       markers
> 
> This change add `obsstore` to the list of files copied during clone. Before this
              adds

> changeset, extinct changeset were copied without their related obsolete marker.
  change,  ..        changesets                 ..                        markers

> Note: extinct changesets were included by such clone prior to this changeset.
                                      .. by clone before this change.

> This is still the case now. There is no strong requirement to exclude obsolete

(Q: Am I right in assuming that "obsolete" is the same as "extinct"? If yes: Why
do you use two different terms here?)

> changesets from the clone as long as they remains obsolete after push. Doing so
          .. from cloning as long as they   remain ..

(Why are you talking about "push" here suddenly? I'm confused...)

> allows to use hard link clone even if obsolete changesets exist on the source.
                hardlink cloning, even ..                         in