New evolve docs, take 2: 1/3: index.rst
Sean Farley
sean.michael.farley at gmail.com
Sat May 31 17:22:46 UTC 2014
Greg Ward writes:
> 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". ;-)
It came from git-land where 'git push -f' is 'unsafe' and can blow your
foot off.
> IMHO "safe" describes both phases (you can't rebase/amend/etc.
> published changesets) and obsolescence (old changesets are still in
> your repository).
Here, "safe" means "safe even if you pushed" while strip means "safe but
only if it's local." I agree with Martin that we can revise this at a
later iteration.
More information about the Evolve-testers
mailing list