You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You should have a basic understanding of what Git is and how it's different from the centralized version control system you may have previously been using.
36
+
You should have a basic understanding of what Git is and how it's different from any centralized version control systems you may have been using previously.
38
37
You should also now have a working version of Git on your system that's set up with your personal identity.
At this point, you can do all the basic local Git operations – creating or cloning a repository, making changes, staging and committing those changes, and viewing the history of all the changes the repository has been through.
38
+
At this point, you can do all the basic local Git operations -- creating or cloning a repository, making changes, staging and committing those changes, and viewing the history of all the changes the repository has been through.
40
39
Next, we'll cover Git's killer feature: its branching model.
41
40
//////////////////////////
42
41
이제 우리는 로컬에서 사용할 수 있는 Git 명령에 대한 기본 지식은 갖추었다. 저장소를 만들고 Clone 하는 방법, 수정하고 나서 Stage 하고 커밋하는 방법, 저장소의 히스토리를 조회하는 방법 등을 살펴보았다.
Copy file name to clipboardExpand all lines: ch04-git-on-the-server.asc
+3-3
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
[#ch04-git-server]
1
+
[[ch04-git-on-the-server]]
2
2
//////////////////////////
3
3
== Git on the Server
4
4
//////////////////////////
@@ -9,7 +9,7 @@
9
9
At this point, you should be able to do most of the day-to-day tasks for which you'll be using Git.
10
10
However, in order to do any collaboration in Git, you'll need to have a remote Git repository.
11
11
Although you can technically push changes to and pull changes from individuals' repositories, doing so is discouraged because you can fairly easily confuse what they're working on if you're not careful.
12
-
Furthermore, you want your collaborators to be able to access the repository even if your computer is offline – having a more reliable common repository is often useful.
12
+
Furthermore, you want your collaborators to be able to access the repository even if your computer is offline -- having a more reliable common repository is often useful.
13
13
Therefore, the preferred method for collaborating with someone is to set up an intermediate repository that you both have access to, and push to and pull from that.
14
14
//////////////////////////
15
15
이 글을 읽는 독자라면 이미 하루 업무의 대부분을 Git으로 처리할 수 있을 거라고 생각한다.
@@ -39,7 +39,7 @@ If you have no interest in running your own server, you can skip to the last sec
39
39
서버를 직접 설치해서 운영할 생각이 없으면 이 장의 마지막 절만 읽어도 된다. 마지막 절에서는 Git 호스팅 서비스에 계정을 만들고 사용하는 방법에 대해 설명한다. 그리고 다음 장에서는 분산 환경에서 소스를 관리하는 다양한 패턴에 대해 논의할 것이다.
40
40
41
41
//////////////////////////
42
-
A remote repository is generally a _bare repository_– a Git repository that has no working directory.
42
+
A remote repository is generally a _bare repository_ -- a Git repository that has no working directory.
43
43
Because the repository is only used as a collaboration point, there is no reason to have a snapshot checked out on disk; it's just the Git data.
44
44
In the simplest terms, a bare repository is the contents of your project's `.git` directory and nothing else.
Copy file name to clipboardExpand all lines: ch05-distributed-git.asc
+2-3
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,12 @@
1
-
[#ch05-distributed-git]
2
-
[[r_distributed_git]]
1
+
[[ch05-distributed-git]]
3
2
//////////////////////////
4
3
== Distributed Git
5
4
//////////////////////////
6
5
== 분산 환경에서의 Git
7
6
8
7
(((distributed git)))
9
8
//////////////////////////
10
-
Now that you have a remote Git repository set up as a point for all the developers to share their code, and you're familiar with basic Git commands in a local workflow, you'll look at how to utilize some of the distributed workflows that Git affords you.
9
+
Now that you have a remote Git repository set up as a focal point for all the developers to share their code, and you're familiar with basic Git commands in a local workflow, you'll look at how to utilize some of the distributed workflows that Git affords you.
11
10
//////////////////////////
12
11
앞 장에서 다른 개발자와 코드를 공유하는 리모트 저장소를 만드는 법을 배웠다. 로컬에서 작업하는 데 필요한 기본적인 명령어에는 어느 정도 익숙해졌다. 이제는 분산 환경에서 Git이 제공하는 기능을 어떻게 효율적으로 사용할지를 배운다.
Copy file name to clipboardExpand all lines: ch10-git-internals.asc
+8-9
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,12 @@
1
-
[#ch10-git-internals]
2
-
[[r_git_internals]]
1
+
[[ch10-git-internals]]
3
2
//////////////////////////
4
3
== Git Internals
5
4
//////////////////////////
6
5
== Git의 내부
7
6
8
7
//////////////////////////
9
-
You may have skipped to this chapter from a previous chapter, or you may have gotten here after reading the rest of the book – in either case, this is where we'll go over the inner workings and implementation of Git.
10
-
We found that learning this information was fundamentally important to understanding how useful and powerful Git is, but others have argued to us that it can be confusing and unnecessarily complex for beginners.
8
+
You may have skipped to this chapter from a much earlier chapter, or you may have gotten here after sequentially reading the entire book up to this point -- in either case, this is where we'll go over the inner workings and implementation of Git.
9
+
We found that understanding this information was fundamentally important to appreciating how useful and powerful Git is, but others have argued to us that it can be confusing and unnecessarily complex for beginners.
11
10
Thus, we've made this discussion the last chapter in the book so you could read it early or later in your learning process.
12
11
We leave it up to you to decide.
13
12
//////////////////////////
@@ -27,13 +26,13 @@ You'll learn more about what this means in a bit.
27
26
28
27
//////////////////////////
29
28
In the early days of Git (mostly pre 1.5), the user interface was much more complex because it emphasized this filesystem rather than a polished VCS.
30
-
In the last few years, the UI has been refined until it's as clean and easy to use as any system out there; but often, the stereotype lingers about the early Git UI that was complex and difficult to learn.
29
+
In the last few years, the UI has been refined until it's as clean and easy to use as any system out there; however, the stereotype lingers about the early Git UI that was complex and difficult to learn.
31
30
//////////////////////////
32
31
Git 초기에는 (1.5 이전 버전) 사용자 인터페이스가 훨씬 복잡했었다. VCS가 아니라 파일 시스템을 강조했기 때문이었다.
33
32
최근 몇 년간 Git은 다른 VCS처럼 쉽고 간결하게 사용자 인터페이스를 다듬어 왔다. 하지만, 여전히 복잡하고 배우기 어렵다는 선입견이 있다.
34
33
35
34
//////////////////////////
36
-
The content-addressable filesystem layer is amazingly cool, so I'll cover that first in this chapter; then, you'll learn about the transport mechanisms and the repository maintenance tasks that you may eventually have to deal with.
35
+
The content-addressable filesystem layer is amazingly cool, so we'll cover that first in this chapter; then, you'll learn about the transport mechanisms and the repository maintenance tasks that you may eventually have to deal with.
37
36
//////////////////////////
38
37
우선 Content-addressable 파일 시스템은 정말 대단한 것이므로 먼저 다룬다. 그리고 나서 데이터 전송 원리를 배우고 마지막에는 저장소를 관리하는 법까지 배운다.
You should have a pretty good understanding of what Git does in the background and, to some degree, how it's implemented.
63
-
This chapter has covered a number of plumbing commands – commands that are lower level and simpler than the porcelain commands you've learned about in the rest of the book.
64
-
Understanding how Git works at a lower level should make it easier to understand why it's doing what it's doing and also to write your own tools and helping scripts to make your specific workflow work for you.
61
+
At this point, you should have a pretty good understanding of what Git does in the background and, to some degree, how it's implemented.
62
+
This chapter has covered a number of plumbing commands -- commands that are lower level and simpler than the porcelain commands you've learned about in the rest of the book.
63
+
Understanding how Git works at a lower level should make it easier to understand why it's doing what it's doing and also to write your own tools and helper scripts to make your specific workflow work for you.
65
64
//////////////////////////
66
65
Git이 내부적으로 어떻게 동작하는지 뿐만 아니라 어떻게 구현됐는지까지 잘 알게 됐을 것이다.
67
66
이 장에서는 저수준 명령어인 Plumbing 명령어를 설명했다. 다른 장에서 우리가 배웠던 Porcelain 명령어보다는 단순하다.
0 commit comments