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, stashing-cleaning.asc, submodules.asc (1,207 words) #77

Merged
merged 4 commits into from Feb 23, 2018

Conversation

heywens
Copy link

@heywens heywens commented Feb 22, 2018

translation for:

  • stashing-cleaning.asc - completed
  • submodules.asc - partial (part 1)

@heywens heywens changed the title TL Localization - Chapter 7, stashing-cleaning.asc [completed], submodules.asc [part1] (1,207 words) TL Localization - Chapter 7, stashing-cleaning.asc, submodules.asc (1,207 words) Feb 22, 2018
If you want an easier way to test the stashed changes again, you can run `git stash branch <branch>`, which creates a new branch for you with your selected branch name, checks out the commit you were on when you stashed your work, reapplies your work there, and then drops the stash if it applies successfully:
Kung ikaw ay nag-stash ng ilang trabaho, iwanan ito sa ilang saglit, at magpatuloy sa branch kung saan ikaw nag-stash ng trabaho, maaari kang magkaroon ng isang problema sa muling paglalapat ng trabaho.
Kung sinusubukan ng paglalapat na baguhin ang isang file na binago mo na, makakakuha ka ng salungatan sa pagsasama-sama at kakailanganin mong lutasin ito.
Kung gusto ang isang mas madaling paraan upang suriing muli ang mga naka-stash na pagbabago, maaari mong patakbuhin ang `git stash branch <branch>`, kung saan ay lumilikha ng isang bagong branch para sa iyo kasama ang iyong napiling pangalan ng branch, nagsusuri sa iyong commit kapag ikaw ay nag-stash ng iyong trabaho, muling naglalapat sa iyong trabaho doon, at pagkatapos ay naghuhulog sa stash kung ito ay matagumpay na nailalapat:

Choose a reason for hiding this comment

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

para sa iyo kasama ang iyong napiling pangalan ng branch to para sa iyong napiling pangalan ng branch

Any file that matches a pattern in your `.gitignore` or other ignore files will not be removed.
If you want to remove those files too, such as to remove all `.o` files generated from a build so you can do a fully clean build, you can add a `-x` to the clean command.
Bilang default, ang utos na `git clean` ay tinatanggal lamang ang mga hindi sinubaybayan na mga file na hindi binabalewala.
Anumang file na tumutugma sa isang pattern sa iyong `.gitignore` o ibang hindi pansinin ng mga file ay hindi matatanggal.

Choose a reason for hiding this comment

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

pattern to hulmahan

If you want to remove those files too, such as to remove all `.o` files generated from a build so you can do a fully clean build, you can add a `-x` to the clean command.
Bilang default, ang utos na `git clean` ay tinatanggal lamang ang mga hindi sinubaybayan na mga file na hindi binabalewala.
Anumang file na tumutugma sa isang pattern sa iyong `.gitignore` o ibang hindi pansinin ng mga file ay hindi matatanggal.
Kung gusto mo na tanggalin din ang mga file na ito, tulad ng tanggalin lahat ang mga file na `.o` na binuo mula sa isang build upang makakagawa ka ng buong malinis na build, maaari kang magdagdag ng `-x` sa clean na utos.

Choose a reason for hiding this comment

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

clean to malinis

----

If you don't know what the `git clean` command is going to do, always run it with a `-n` first to double check before changing the `-n` to a `-f` and doing it for real.
The other way you can be careful about the process is to run it with the `-i` or ``interactive'' flag.
Kung hindi mo alam kung ano ang gagawin ng command na `git clean`, palaging patakbuhin ito ng may isang` -n` muna upang mag-double check bago baguhin ang `-n` sa isang` -f` at gagawain ito sa totoo.

Choose a reason for hiding this comment

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

command to utos

----

If you don't know what the `git clean` command is going to do, always run it with a `-n` first to double check before changing the `-n` to a `-f` and doing it for real.
The other way you can be careful about the process is to run it with the `-i` or ``interactive'' flag.
Kung hindi mo alam kung ano ang gagawin ng command na `git clean`, palaging patakbuhin ito ng may isang` -n` muna upang mag-double check bago baguhin ang `-n` sa isang` -f` at gagawain ito sa totoo.

Choose a reason for hiding this comment

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

mag-double check to dobleng pagsuri


This will run the clean command in an interactive mode.
Papatakbuhin nito ang clean na uto sa isang interactive na mode.
Copy link

Choose a reason for hiding this comment

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

clean to malinis
uto to utos

6: help
What now>
*** Mga kautusan ***
1: clean 2: mag-filter gamit ang pattern 3: pumili ng mga numero 4: tanungin ang bawat isa 5: huminto

Choose a reason for hiding this comment

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

pattern to hulmahan

Perhaps it’s a library that a third party developed or that you’re developing separately and using in multiple parent projects.
A common issue arises in these scenarios: you want to be able to treat the two projects as separate yet still be able to use one from within the other.
Madalas na nangyayari na habang nagtatrabaho sa isang proyekto, kailangan mong gumamit ng isa pang proyekto mula sa loob nito.
Marahil ito ay isang library na binuo ng isang third party o ikaw ay hiwalay lumilikha at ginagamit sa maraming mga proyektong magulang.

Choose a reason for hiding this comment

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

third party to ikatlong partido

First you should notice the new `.gitmodules` file.
This is a configuration file that stores the mapping between the project’s URL and the local subdirectory you’ve pulled it into:
Una dapat mong mapansin ang bagong file na `.gitmodules`.
Ito ay isang file ng pagsasaayos na nag-iimbak sa pag-map sa pagitan ng URL ng proyekto at ang lokal na subdirectory na na-pull mo ito:

Choose a reason for hiding this comment

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

pag-map to pagmapa

You can overwrite this value locally with `git config submodule.DbConnector.url PRIVATE_URL` for your own use.
When applicable, a relative URL can be helpful.
Dahil ang URL sa file na .gitmodules ay kung ano ang unang subukan ng mga tao upang i-clone/i-fetch, siguraduhin na gumamit ng isang URL na maaari nilang ma-access kung posible.
Halimbawa, kung gumamit ka ng isang iba't ibang URL upang mag-push kaysa sa iba na gusto na mag-pull, gumamit ng isa na may access ang iba.

Choose a reason for hiding this comment

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

access to pahintulot

When applicable, a relative URL can be helpful.
Dahil ang URL sa file na .gitmodules ay kung ano ang unang subukan ng mga tao upang i-clone/i-fetch, siguraduhin na gumamit ng isang URL na maaari nilang ma-access kung posible.
Halimbawa, kung gumamit ka ng isang iba't ibang URL upang mag-push kaysa sa iba na gusto na mag-pull, gumamit ng isa na may access ang iba.
Maaari mong i-overwrite ang halaga na ito nang lokal gamit ang `git config submodule.DbConnector.url PRIVATE_URL` para sa pansariling paggamit.

Choose a reason for hiding this comment

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

i-overwrite to sapawan

@mind-blast
Copy link

Please check on my suggested words. Thank you.

@heywens
Copy link
Author

heywens commented Feb 23, 2018

Hi Sir @Robin-Ho, thanks for the review.
I have applied above suggestions except translating the following words:

  • pattern
  • third party

Thanks!

@severinolorillajr severinolorillajr merged commit b02b799 into progit2-tl:master Feb 23, 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
3 participants