On 7/9/17 10:16 PM, Sean Farley wrote:
Jun Wu <qu...@fb.com> writes:
hash-preserving obsstore,
I've commented on this before but I will try to be as explicit as
possible here.
I do not want to think about hash-preserving obsstore right now.
I'm speaking from the point of view of someone who uses obsolete markers
but isn't involved in the day to day design work.
I do want us to think about it, actually.
I do not want to think about it for the next year even.
I want obs-exchange to solved before hash-preserving.
I want all the UI/UX of evolve to be solve and in core before we even
*contemplate* (the over-engineered) hash-preserving.
Hash preservation (or not) is necessarily one of the core tenets of any
UX based around obsolete markers. This isn't about whether it's
overengineered -- this is about whether it makes sense to users, and
whether an "hg undo" command brings you back to the same hash or not is
one of the more fundamental design decisions to make.
It's usually a good practice to first determine what users expect and
work backwards from there.
- Siddharth
I don't know how to be more clear with you while still being polite.
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
