New evolve docs, take 2: 1/3: index.rst

Greg Ward greg at gerg.ca
Sat May 31 12:37:41 UTC 2014


On 31 May 2014, Martin Geisler said:
> I'm actually confused why you would call one safer than the other.
> Safety doesn't seem like the diffenting factor to me. Both mechanisms
> leave the data behind: strip places the old data in external bundle
> files and evolve leaves the data in the repository, but marked obsolete.

I'm not sure who started using the phrase "safe mutable history". I'm
pretty sure it wasn't me; I just adopted it because it's a nice
tagline. Beats "mutable history without fiddly little bundle files
that you lose track of because the filenames are unhelpful". ;-)

IMHO "safe" describes both phases (you can't rebase/amend/etc.
published changesets) and obsolescence (old changesets are still in
your repository).

Anyways, I completely agree with you that the old strip model isn't
unsafe per se. I just think obsolescence is safer.

I do want to make sure that the new docs describe the new way. There
is no need to describe how strip works in the docs for evolve; it's
just irrelevant.

       Greg
-- 
Greg Ward                            http://www.gerg.ca
<greg at gerg.ca>                       @gergdotca



More information about the Evolve-testers mailing list