On Mon, Jun 28, 2021 at 5:49 AM Raphaël Gomès <raphael.go...@octobus.net> wrote: > > To Matt Harbison: you said something about storing exec bit and symlink > info explicitly to help platforms like Windows that don't have them, > could you please elaborate?
The idea is essentially this, without having to steal undefined/undocumented bits: https://www.mercurial-scm.org/wiki/DirState#Proposed_extensions I'm not sure what the point of having fallback vs real(?) bits was, but I guess it could be useful to disambiguate on a system that *does* support +x or symlink. Support for this would fix issue2020, issue5883, and maybe a few other corner cases. > As a general recap (and to help understand some decisions), the new > format will be an append-only tree with no stem compression for > performance reasons. The Python implementation will be functional but > very basic and will offer no purposeful performance improvements (unless > someone wants to have fun!), as we currently only have the bandwidth for > optimizing the Rust implementation. Is a toggle-able bit like this a hassle for an append-only data structure? I suppose it's not much different than adding and removing a file several times, but I haven't paid a lot of attention to this discussion up to this point. _______________________________________________ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
