On 14/10/19 10:55AM, Jiang Xin wrote: > 김건우 <rlarjsdn122@xxxxxxxxx> 于2019年10月10日周四 上午12:02写道： > > > > Hello. > > > > I have a question whether the GIT GUI project still in progress or not > > because I want to contribute to translating GIT GUI into Korean. I asked > > prati0100 who is a maintainer of GIT GUI on > > Github(https://github.com/prati0100/git-gui), but he doesn't know the > > project is on. > > If the project is in progress, please reply this E-mail with how to > > contribute the GIT GUI for translation. > > > > Thank you. > > > > -- > > Signed-off-by: Kim Geonwoo (김건우)<rlarjsdn122@xxxxxxxxx> > > > > Git GUI is a stand-alone project which is periodically merged to Git > project by a subtree merge. According to the latest > SubmittingPatches[1] documentation, git-gui is managed by Pratyush > Yadav in a separate project[2]. > > As a separate project, the git-l10n project will merge l10n > contributions into itself and then merge them to Git as a whole > through a subtree merge. As what README.md[3] of git-gui says, > contributing to git-gui should using mailing list. This means l10n > contributors for git-guil, have to use git-format-patch and git > send-email commands to send patches to the mailing list, which is > inconvenience for git-gui l10n contributors. I suppose using a > dedicate git-guil l10n coordinator repository or simply using pull > requests of "prati0100/git-gui" as the l10n contribution workflow, > @Yadav. I'd prefer a separate git-gui l10n repo. The translators can use whatever workflow they prefer, and then I can just directly merge in your pull requests, similar to how it works for Git. Does this work for you guys? Thanks for volunteering to do the translations :) > [1] https://github.com/git/git/blob/master/Documentation/SubmittingPatches#L375 > [2] https://github.com/prati0100/git-gui > [3] https://github.com/prati0100/git-gui/blob/master/README.md -- Regards, Pratyush Yadav
