@@ -49,10 +49,10 @@ Okay, so you have decided on the proper branch. Create a feature branch
49
49
and start hacking:
50
50
51
51
```
52
- $ git checkout -b my-feature-branch -t origin/v0.8
52
+ $ git checkout -b my-feature-branch -t origin/v0.10
53
53
```
54
54
55
- (Where v0.8 is the latest stable branch as of this writing.)
55
+ (Where v0.10 is the latest stable branch as of this writing.)
56
56
57
57
58
58
### COMMIT
@@ -68,14 +68,15 @@ Writing good commit logs is important. A commit log should describe what
68
68
changed and why. Follow these guidelines when writing one:
69
69
70
70
1 . The first line should be 50 characters or less and contain a short
71
- description of the change.
71
+ description of the change prefixed with the name of the changed
72
+ subsystem (e.g. "net: add localAddress and localPort to Socket").
72
73
2 . Keep the second line blank.
73
74
3 . Wrap all other lines at 72 columns.
74
75
75
76
A good commit log looks like this:
76
77
77
78
```
78
- Header line : explaining the commit in one line
79
+ subsystem : explaining the commit in one line
79
80
80
81
Body of commit message is a few lines of text, explaining things
81
82
in more detail, possibly giving some background about the issue
@@ -99,7 +100,7 @@ Use `git rebase` (not `git merge`) to sync your work from time to time.
99
100
100
101
```
101
102
$ git fetch upstream
102
- $ git rebase upstream/v0.8 # or upstream/master
103
+ $ git rebase upstream/v0.10 # or upstream/master
103
104
```
104
105
105
106
0 commit comments