Thanks for the history. It’s taken many turns, I wasn’t there, and branch plan is now being discussed.
Historically, it seems like we had branches for features and large changes, ideally merged to master.
There’s a proposal to flip that, but I’m not really convinced. As a big change, your input is valuable…
Refreshing a repository after changing line endings sounds severe. Is there a better path to “better”?
Sorry I’m not a GitHub guru, but I do expect we’ll have to support devs on different line-end systems.
Can you expand on that? I don’t think this is SEE. The problem is that they removed old code that we use, meaning we’re stuck on an old System.Data.SQLite until we can find how to get encryption back.