What is the translation of " GIT-U " in English?

• git

Examples of using Git-u in Slovenian and their translations into English

Privzeto ime veje v Git-ujemaster.
The default branch name in Git is master.

Dajanje datoteke v vmesno fazo jo označi kot rešeno v Git-u.
Staging the file marks it as resolved in Git.

To lahko naredimo v Git-u z git read-tree.
We can do that in Git with git read-tree.

Veja v Git-u je enostavno lahek prenosen kazalec k enemu od teh pošiljanj.
Branch in Git means a lightweight movable pointer to one of these commits.

To naredi združevanje veliko bolj enostavno v Git-u kot v teh starejših sistemih.
This makes merging a heck of a lot easier in Git than in these other systems.

V Git-u sta dva glavna načina za integracijo sprememb iz ene veje v drugo: merge in rebase.
In Git, there are two main ways to integrate changes from one branch into another: the merge and the rebase.

Preklop -M pove Git-u, da išče preimenovanja.
The-M switch tells Git to look for renames.

To lahko vzame nekaj sekund ali celo minut, odvisno od velikosti projekta, kjer je v Git-u proces vedno takojšnji.
This can take several seconds or even minutes, depending on the size of the project, whereas in Git the process is always instantaneous.

Prisotnost te datoteke pove Git-u, da je v redu ponuditi ta projekt brez overjanja.
The presence of that file tells Git that it's OK to serve this project without authentication.

Čeprav Subversion avtmoatično naredi to združevanje na strežniku, če so urejene različne datoteke, morate v Git-u združevati pošiljanja lokalno.
Although Subversion automatically does such a merge on the server if different files are edited, in Git you must merge the commits locally.

Če pričenjate slediti obstoječi projekt v Git-u, boste morali iti v direktorij projekta in vpisati.
If you're starting to track an existing project in Git, you need to go to the project's directory.

Prva vrstica pove Git-u, naj ignorira katerekoli datoteke, ki se končajo z“. o” ali“. a”- objekti in arhivske datoteke, ki so lahko produkt gradnje vaše kode.
The first line tells Git to ignore any files ending in“. o” or“. a”- object and archive files that may be the product of building your code.

Te zgoščene vrednosti boste videli v Git-u vse povsod, ker jih veliko uporablja.
You will see these hash values all over the place in Git because it uses them so much.

Večina operacij v Git-u potrebuje za delovanje samo lokalne datoteke in vire- v splošnem ni potrebnih nobenih informacij iz drugega računalnika na vašem omrežju.
Most operations in Git only need local files and resources to operate- generally no information is needed from another computer on your network.

Vendar, da naredite kakršno koli sodelovanje v Git-u, boste potrebovali imeti oddaljeni Git repozitiorij.
However, in order to do any collaboration in Git, you will need to have a remote Git repository.

To je 40-znakovni niz sestavljen iz znakov šestnajstiškega zapisa(0-9 in a-f) in preračunan na osnovi vsebine datoteke ali strukture direktorijev v Git-u.
This is a 40-character string composed of hexadecimal characters(0- 9 and a- f) and calculated based on the contents of a file or directory structure in Git.

To je glavna stvar, ki si jo morate zapomniti o Git-u, če želite, da gre preostanek procesa učenja gladko.
This is the main thing to remember about Git if you want the rest of your learning process to go smoothly.

Ker je veja v Git-u dejansko enostavna datoteka, ki vsebuje 40 znakovno SHA-1 preverjeno vsoto pošiljanja, kamor kaže, so veje poceni za izdelati in uničiti.
Because a branch in Git is actually a simple file that contains the 40 character SHA-1 checksum of the commit it points to, branches are cheap to create and destroy.

To je glavna stvar, ki si jo morate zapomniti o Git-u, če želite, da gre preostanek procesa učenja gladko.
Pay attention now- here is the main thing to remember about Git if you want the rest of your learning process to go smoothly.

Druga vrstica pove Git-u naj ignorira vse datoteke, ki se končajo s tildo(~), ki je uporabljena s strani mnogih tekstovni urejevalnikov kot je Emacs, da označuje začasne datoteke.
The second line tells Git to ignore all files that end with a tilde(~), which is used by many text editors such as Emacs to mark temporary files.

Ti kanali so pogosto napolnjeni s stotinami ljudi, ki velik ovedo o Git-u in so pogosto pripravljeni pomagati.
These channels are regularly filled with hundreds of people who are all very knowledgeable about Git and are often willing to help.

Ta koncept je tako resničen v Git-u kot tudi v Subversion-u(ali kateremkoli drugem CVCS-ju) in ta model deluje odlično v Git-u.
This concept is as true in Git as it is in Subversion(or any CVCS), and this model works perfectly well in Git.

Repozitorij na NFS je pogostokrat počasnejši kot repozitorij preko SSH na istem strežniku, kar omogoča Git-u, da poganja lokalne diske na vsakem sistemu.
A repository on NFS is often slower than the repository over SSH on the same server, allowing Git to run off local disks on each system.

Ukaz replace vam omogoča določiti objekt v Git-u in povedati"vsakič ko to vidite, se pretvarjaj, da gre za drugo stvar".
The replace command lets you specify an object in Git and say"every time you see this, pretend it's this other thing".

Vendar v Git-u vsak razvijalec je potencialno oboje vozlišče in središče- to je, vsak razvijalec lahko tako prispeva kodo k drugim repozitorijem in vzdržuje javen repozitorij na katerem ostali lahko osnujejo svoje delo in h katerem lahko prispevajo.
In Git, however, every developer is potentially both a node and a hub- that is, every developer can both contribute code to other repositories and maintain a public repository on which others can base their work and which they can contribute to.

Na tej točki, bi morali biti zmožni narediti večino stvari v Git-u, ki jih boste potrebovali v ukazni vrstici dan za dnem in se s tem počutite udobno.
At this point, you should be able to do most of the things in Git that you will need on the command line day to day and feel comfortable doing so.

Počutiti se bi morali dokaj udobno pri prispevanju k projektu v Git-u kot tudi pri vzdrževanju vašega lastnega projekta in povezovanju prispevkov ostalih uporabnikov.
Summary You should feel fairly comfortable contributing to a project in Git as well as maintaining your own project or integrating other users' contributions.