質問編集履歴
2
fix text
test
CHANGED
|
File without changes
|
test
CHANGED
|
@@ -10,11 +10,9 @@
|
|
|
10
10
|
|
|
11
11
|
|
|
12
12
|
|
|
13
|
-
通常`git checkout`はブランチを切り替える目的で使い、リビジョンを引数に指定しますが、`git checkout .`では何を指定しているのでしょうか。
|
|
13
|
+
通常`git checkout`はブランチを切り替える目的で使い、リビジョンを引数に指定しますが、`git checkout .`では何を指定しているのでしょうか。ピリオドがHEADを指すわけでもないようですね。（下記）
|
|
14
14
|
|
|
15
15
|
|
|
16
|
-
|
|
17
|
-
`git checkout HEAD`と`git checkout .`
|
|
18
16
|
|
|
19
17
|
|
|
20
18
|
|
1
テストの追加
test
CHANGED
|
File without changes
|
test
CHANGED
|
@@ -4,6 +4,116 @@
|
|
|
4
4
|
|
|
5
5
|
|
|
6
6
|
|
|
7
|
-
git checkout .（ピリオド）
|
|
7
|
+
`git checkout .`（ピリオド）
|
|
8
8
|
|
|
9
|
-
git reset --hard HEAD
|
|
9
|
+
`git reset --hard HEAD`
|
|
10
|
+
|
|
11
|
+
|
|
12
|
+
|
|
13
|
+
通常`git checkout`はブランチを切り替える目的で使い、リビジョンを引数に指定しますが、`git checkout .`では何を指定しているのでしょうか。同じcheckoutコマンドにもかかわらず動作が異なるように見えるので気になります。
|
|
14
|
+
|
|
15
|
+
|
|
16
|
+
|
|
17
|
+
`git checkout HEAD`と`git checkout .`
|
|
18
|
+
|
|
19
|
+
|
|
20
|
+
|
|
21
|
+
```bash
|
|
22
|
+
|
|
23
|
+
$ git status
|
|
24
|
+
|
|
25
|
+
On branch branch_a
|
|
26
|
+
|
|
27
|
+
Changes to be committed:
|
|
28
|
+
|
|
29
|
+
(use "git reset HEAD <file>..." to unstage)
|
|
30
|
+
|
|
31
|
+
|
|
32
|
+
|
|
33
|
+
modified: aaaa
|
|
34
|
+
|
|
35
|
+
|
|
36
|
+
|
|
37
|
+
Changes not staged for commit:
|
|
38
|
+
|
|
39
|
+
(use "git add <file>..." to update what will be committed)
|
|
40
|
+
|
|
41
|
+
(use "git checkout -- <file>..." to discard changes in working directory)
|
|
42
|
+
|
|
43
|
+
|
|
44
|
+
|
|
45
|
+
modified: cccc
|
|
46
|
+
|
|
47
|
+
|
|
48
|
+
|
|
49
|
+
$ git checkout .
|
|
50
|
+
|
|
51
|
+
$ git status
|
|
52
|
+
|
|
53
|
+
On branch branch_a
|
|
54
|
+
|
|
55
|
+
Changes to be committed:
|
|
56
|
+
|
|
57
|
+
(use "git reset HEAD <file>..." to unstage)
|
|
58
|
+
|
|
59
|
+
|
|
60
|
+
|
|
61
|
+
modified: aaaa
|
|
62
|
+
|
|
63
|
+
|
|
64
|
+
|
|
65
|
+
$ touch dddd
|
|
66
|
+
|
|
67
|
+
$ git status
|
|
68
|
+
|
|
69
|
+
On branch branch_a
|
|
70
|
+
|
|
71
|
+
Changes to be committed:
|
|
72
|
+
|
|
73
|
+
(use "git reset HEAD <file>..." to unstage)
|
|
74
|
+
|
|
75
|
+
|
|
76
|
+
|
|
77
|
+
modified: aaaa
|
|
78
|
+
|
|
79
|
+
|
|
80
|
+
|
|
81
|
+
Untracked files:
|
|
82
|
+
|
|
83
|
+
(use "git add <file>..." to include in what will be committed)
|
|
84
|
+
|
|
85
|
+
|
|
86
|
+
|
|
87
|
+
dddd
|
|
88
|
+
|
|
89
|
+
|
|
90
|
+
|
|
91
|
+
$ git checkout HEAD
|
|
92
|
+
|
|
93
|
+
M aaaa
|
|
94
|
+
|
|
95
|
+
$ git status
|
|
96
|
+
|
|
97
|
+
On branch branch_a
|
|
98
|
+
|
|
99
|
+
Changes to be committed:
|
|
100
|
+
|
|
101
|
+
(use "git reset HEAD <file>..." to unstage)
|
|
102
|
+
|
|
103
|
+
|
|
104
|
+
|
|
105
|
+
modified: aaaa
|
|
106
|
+
|
|
107
|
+
|
|
108
|
+
|
|
109
|
+
Untracked files:
|
|
110
|
+
|
|
111
|
+
(use "git add <file>..." to include in what will be committed)
|
|
112
|
+
|
|
113
|
+
|
|
114
|
+
|
|
115
|
+
dddd
|
|
116
|
+
|
|
117
|
+
|
|
118
|
+
|
|
119
|
+
```
|