Hello Alexei and all:
What you said, is just my mean.
I will create a new freetype repository. And here is my steps for each festure:
1, Check in the latest freetype code (release or dev version ? I will use release first).
2, Add code for a new feature.
3, Then notify you the new feature, and you check it:
If has any problem, notify me to modify.
If passed, you add code to your dev version( and send to me ?). Then we work on next feature.
I have many respects on your work for freetype. So I want contribute my efforts to freetype.
Many Thanks.
Liu Kunpeng(柳鲲鹏)
TSIT(泰山信息科技)
2022-09-25
------------------------------------------------------------------
发件人：Alexei Podtelezhnikov <apodtele@gmail.com>
发送时间：2022年9月24日(星期六) 21:16
收件人：柳鲲鹏 <liukunpeng@ts-it.cn>
抄 送：Werner LEMBERG <wl@gnu.org>; freetype-devel <freetype-devel@nongnu.org>
主 题：Re: This is freetype sourcecode from TSIT(I made many improvements)
> I really love freetype very much, so I want to make it more powerful and.
> Waiting for your plan.
I already told you that you have to reorganize your code into smaller
individual contributions. You have a nice list of changes. Each of the
list items has to be presented separately either as a diff patch or a
git commit in your git clone, or a merge request . What you have in
your git repository is everything together. We cannot consider this
seriously. I also told you that you should avoid renaming functions or
introducing synonymous functions.The plan is small steps with good
rationale, not just "It is more convenient for me to name it
differently". You do not have to contribute everything at once. It
might take a lot of steps over a long period of time.
Alexei