Kotatogram Dev Blog

I've updated the sources to 4.15.1, will publish them after the test build.

Since the version is already beyond 4.14, and I don’t want to create a branch for each version since it will bloat the repository, this branch will be called patches-track-wip .

Also, to reduce the size of the repository, I plan to reorganize the patches-track* branches.

How it looks now:

— patches-track: TD 4.1.1
— patches-track-old: TD 3.5.2
— patches-track-4.8.4: TD 4.8.4
— patches-track-4.14: TD 4.14.13

How I want to do:

— patches-track: TD 3.5.2
— patches-track-wip: TD 4.15.1
— patches-track-old, patches-track-4.8.4 and patches-track-4.14 will be deleted (or archived, if needed).

So if you need versions based on 4.1.1, 4.8.4 or 4.14.13, I advise you to fork these branches. Or if you want them to stay a little longer, let me know at @kotatochat.

www.tg-me.com/it/telegram/com.kotatogram_dev/17

2.7K viewsedited  Mar 11, 2024 at 22:35

I've updated the sources to 4.15.1, will publish them after the test build.

Since the version is already beyond 4.14, and I don’t want to create a branch for each version since it will bloat the repository, this branch will be called patches-track-wip .

Also, to reduce the size of the repository, I plan to reorganize the patches-track* branches.

How it looks now:

— patches-track: TD 4.1.1
— patches-track-old: TD 3.5.2
— patches-track-4.8.4: TD 4.8.4
— patches-track-4.14: TD 4.14.13

How I want to do:

— patches-track: TD 3.5.2
— patches-track-wip: TD 4.15.1
— patches-track-old, patches-track-4.8.4 and patches-track-4.14 will be deleted (or archived, if needed).

So if you need versions based on 4.1.1, 4.8.4 or 4.14.13, I advise you to fork these branches. Or if you want them to stay a little longer, let me know at @kotatochat.

BY Kotatogram Dev Blog