New evolve docs: sharing guide

timeless at gmail.com timeless at gmail.com
Sun Jun 15 02:53:24 UTC 2014


> This time, all the tests pass, so no further /amendment/ is required.

I'd sort of favor "amending"

> /None of/ our missteps /or/ amendments are
visible publicly, just the final, beautifully polished changeset:

Neither - nor

---
> There is one important step left to do. Because we pushed from
> ``test-repo`` to ``public``, the pushed changeset is in *public* phase
> in those two repositories. But ``dev-repo`` knows nothing of this:
> that changeset is still *draft* there. If we're not careful, we might
> mutate history in ``dev-repo``, obsoleting a changeset that is already
> public. Let's avoid that situation for now by pulling from
> ``test-repo`` down to ``dev-repo``::
>
>  $ cd ../dev-repo
>  $ hg pull -u
>  [...]
>  no changes found
> Even though no *changesets* were pulled, Mercurial still pulled
> obsolescence markers from ``test-repo``.

I'm assuming this means my next amend attempt over my current version will fail. That's surprising. Doesn't this argue in favor of telling me that my current version has changed states?  
---
Please be consistent about capitalizing people (when you mean the people and not their repositories) or not capitalizing them at all. 
‎



More information about the Evolve-testers mailing list