# Kestrel is coming

**URL:** <https://forum.duplicati.com/t/kestrel-is-coming/15527>\
**Category:** Developer\
**Created:** [December 30, 2022, 7:07pm UTC](https://forum.duplicati.com/t/kestrel-is-coming/15527 "2022-12-30T19:07:50Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![ts678](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/t/8491ac/32.png) [@ts678](https://forum.duplicati.com/u/ts678)\
**Post date:** [May 2, 2023, 5:07pm UTC](https://forum.duplicati.com/t/kestrel-is-coming/15527/18 "2023-05-02T17:07:49Z")

</div>

> [@tsuckow](#):
>
> I tracked down when I gave up on coexisting.

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](https://forum.duplicati.com/t/branching-model-proposal/16212), but I’m not really convinced. As a big change, your input is valuable…

> [@tsuckow](#):
>
> the duplicati repository does not have a gitattributes file normalizing line endings

[Refreshing a repository after changing line endings](https://docs.github.com/en/get-started/getting-started-with-git/configuring-git-to-handle-line-endings#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.

> [@tsuckow](#):
>
> Also be aware that my branch does not support encryption/password on sqllite for reasons of nebulous licensing.

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.

[Which tool can open encrypted DB](https://forum.duplicati.com/t/which-tool-can-open-encrypted-db/2372/17)

---

_[View the full topic](https://forum.duplicati.com/t/kestrel-is-coming/15527)._