Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Analyze and resolve two conflicts on two commits - Indonesian #763

Open
swfsql opened this issue Feb 12, 2018 · 3 comments
Open

Analyze and resolve two conflicts on two commits - Indonesian #763

swfsql opened this issue Feb 12, 2018 · 3 comments

Comments

@swfsql
Copy link
Contributor

swfsql commented Feb 12, 2018

One commit inserted a conflict:
#660

And then another one tried to solve the inesrted conflict, when there was yet another conflict:
#668

The file should be analyzed to see if there is information duplication, or missing information.

File was safe after this commit:
#728

@Pastipas
Copy link

Pastipas commented Feb 12, 2018

Hi @swfsql Sorry for interrupting, if we want to contribute who we should contact for, so he/she could direct us to file that need to be translate and make sure that will be no conflict with other. I have experience translating the file but found out later that some one else also working on it. resulting in PR conflict,

@swfsql
Copy link
Contributor Author

swfsql commented Jun 23, 2019

Hello Patispas, I'm sorry for the delay in responding. Conflicts tend to be common since we were not trying to coordinate who would translate what.

This project is halted for a while now, and since there are no more rewards from utopian, I guess that my response is of no use now.

Thanks for trying to contact.

@swfsql swfsql closed this as completed Jun 23, 2019
@swfsql
Copy link
Contributor Author

swfsql commented Jun 23, 2019

Reopened since this is a issue regarding translation content

@swfsql swfsql reopened this Jun 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants