On Thu, 2016-02-18 at 14:12 +0100, Laszlo Ersek wrote: > > > And even if we've missed the chance to do it "in retrospect" for > > historical commits in our canonical git repository, we could still make > > a commit now which *changes* the line endings to what git expects, and > > quite soon this whole nonsense would be a thing of the past. > > Yes. I think that would take a commit that converted everything to > LF-only. Then everybody on Windows would have to toggle some git knobs, > correct? Would that be safe when moving between commits?
I'm not even sure if they'd have to toggle anything. Doesn't git convert automatically if it finds LF in the files it checks out, on Windows? And if things do get checked out with LF-only line endings on Windows, isn't that *also* harmless? I have fairly much reached my masochism quota for this week though; I'm not about to attempt to boot a Windows machine and check :) Either way, such a change will be *very* quickly lost in the dim and distant past — rather than being a constant problem and a barrier to contributions. -- David Woodhouse Open Source Technology Centre [email protected] Intel Corporation
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
