Hi,
Thanks for the answers and comments.
> Yes, I agree that it probably would be much better to go back to use
> dulwich both for protocol serving and for providing data for the web
> frontend, instead of forking out to git. Disclaimer: I don't know has
> fast dulwich is these days. It could
Digging a bit deeper:
- The changeset that you linked
(https://kallithea-scm.org/repos/kallithea/changeset/034e4fe1ebb2#rhodecodelibsubprocessiopy_n127)
actually shows that historically it went the other way round, that is at first
dulwich's server was used but then considered "buggy",
Hi Mads,
I can try that, but I'm a bit worried that it is monkey-patching and
half-solving at best. And the fact that this area is considered "obscure code"
is even worse.
Trying to get a broader picture: There are comments like `TODO: This function
now uses os underlying 'git' command which
Hi,
When cloning a medium-sized repo (not extremely large but with a couple heavy
media files), I consistently get a timeout preventing the cloning from
completing.
Client:
> $ git clone https://user@domain/main_website
> Cloning into 'main_website'...
> Password for 'https://user@domain':
>
Hi Mads,
Thanks for the answer.
Yes, `i18n.native = en` works for me! Thanks for the hint.
Your patch works as well and LGTM.
Kind regards,
Quentin
___
kallithea-general mailing list
kallithea-general@sfconservancy.org
Hi,
I'm new to Kallithea. I freshly installed an instance and got an issue with
languages.
My browser sends the following header:
Accept-Language: en-US,en;q=0.7,fr-CH;q=0.3
I expect Kallithea to be rendered in English, but instead I see French.
I found in the mail archive that the issue has
