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

TL Localization - Chapter 7, Submodules (1,112 words) #84

Merged
merged 2 commits into from
Feb 28, 2018

Conversation

heywens
Copy link

@heywens heywens commented Feb 27, 2018

Hi, kindly check my contribution. Thanks!

Copy link

@cherryloua cherryloua left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @heywens

I have a few suggestions that you might like to consider.

Here we'll see that there was a change on the server for this submodule and it gets merged in.
Subukan natin ito sa opsyon na ``merge''.
Upang itakda ito nang manu-mano, maaari lamang nating idagdag ang pagpipilian na `--merge` sa ating `update` na pagtawag.
Dito, makikita natin na may isang pagbabago sa server para sa submodule na ito at ito ay nai-merge.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please, change "manu-mano" to "mano-mano" base on Google Translate and Glosbe it was spelled like that.


[[_publishing_submodules]]
===== Publishing Submodule Changes
===== Paglalahatla sa mga Pagbabago ng Submodule

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Paglalahatla" to "Paglalathala"

Now we have some changes in our submodule directory.
Some of these were brought in from upstream by our updates and others were made locally and aren't available to anyone else yet as we haven't pushed them yet.
Ngayon ay mayroon ng tayo iilang mga pagbabago sa ating submodule na direktoryo.
Ilan sa mga ito ay dinala mula sa upstream sa pamamagitan ng ating mga update at ang iba ay ginawa sa lokal at hindi pa magagamit ng sinuman dahil hindi pa natin na-push ang mga ito.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"mayroon ng tayo" to "mayroon na tayong"

If we commit in the main project and push it up without pushing the submodule changes up as well, other people who try to check out our changes are going to be in trouble since they will have no way to get the submodule changes that are depended on.
Those changes will only exist on our local copy.
Kung tayo ay nag-commit sa pangunahing proyekto at pi-nush ito, nang wala ring pag-push sa mga pagbabago ng submodule, ang ibang tao na nagsusubok na mag-check out ng mga pagbabago ay magkakaroon ng problema dahil wala silang paraan upang makuha ang mga naka-dependeng pagbabago sa submodule.
Ang mga pagbabago iyon ay umiiral lamang sa ating lokal na kopya.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"mga pagbabago iyon" to "mga pagbabagong iyon"

In order to make sure this doesn't happen, you can ask Git to check that all your submodules have been pushed properly before pushing the main project.
The `git push` command takes the `--recurse-submodules` argument which can be set to either ``check'' or ``on-demand''.
The ``check'' option will make `push` simply fail if any of the committed submodule changes haven't been pushed.
Para makasiguro na hindi na ito mangyayari, maaari mong hilingin ang Git na suriin na ang lahat ng iyong mga submodile ay na-push nang maayos bago mag-push sa pangunahing proyekto.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"maaari mong hilingin ang Git" to "maaari mong hilingin sa Git" not really sure... but the later sounds better, I guess.

The `git push` command takes the `--recurse-submodules` argument which can be set to either ``check'' or ``on-demand''.
The ``check'' option will make `push` simply fail if any of the committed submodule changes haven't been pushed.
Para makasiguro na hindi na ito mangyayari, maaari mong hilingin ang Git na suriin na ang lahat ng iyong mga submodile ay na-push nang maayos bago mag-push sa pangunahing proyekto.
Ang utos `git push` ay tumatanggap ng argumento na `--recurse-submodules` na kung saan maaari itakda alinman sa ``check'' o ``on-demand''.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"na kung saan maaari itakda alinman sa" to "na kung saan ay maaaring itakda ang alinman sa"


[source,console]
----
$ git push --recurse-submodules=check
The following submodule paths contain changes that can
not be found on any remote:
Ang mga sumusunod na mga path ng submodule ay naglalaman ng mga pagbabago na maaari

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"na maaari" change to "na maaaring"

The simple option is to go into each submodule and manually push to the remotes to make sure they're externally available and then try this push again.
If you want the check behavior to happen for all pushes, you can make this behavior the default by doing `git config push.recurseSubmodules check`.
Tulad ng iyong nakikita, nagbibigay din ito sa atin ng ilang kapaki-pakinabang na payo tungkol sa kung ano ang maaari nating gawin sa susunod.
Ang simpleng pagpipilian ay pumunta sa bawat submodule at manu-manong i-push sa mga remote upang matiyak na magagamit ang mga ito sa labas at pagkatapos ay subukang muli ang push na ito.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"manu-manong" change to "mano-manong"

@heywens
Copy link
Author

heywens commented Feb 28, 2018

Hi @cherryloua, thank you very much for the review. Necessary changes have been applied.

Thank you.

@severinolorillajr severinolorillajr merged commit 7ec916a into progit2-tl:master Feb 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants