- Notifications
You must be signed in to change notification settings - Fork5
Commit899beb7
committed
Still more tweaking of git_changelog.
1. Don't assume there's only one candidate match; check them all and use theone with the closest timestamp. Avoids funny output when someone makesseveral successive commits with the same log message, as certain peoplehave been known to do.2. When the same commit (with the same SHA1) is reachable from multiplebranch tips, don't report it for all the branches; instead report it onlyfor the first such branch. Given our development practices, this casearises only for commits that occurred before a given branch split off frommaster. The original coding blamed old commits on *all* the branches,which isn't terribly useful; the new coding blames such a commit only onmaster.1 parent30d2e10 commit899beb7
1 file changed
+19
-5
lines changedLines changed: 19 additions & 5 deletions
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
47 | 47 |
| |
48 | 48 |
| |
49 | 49 |
| |
50 |
| - | |
51 | 50 |
| |
52 | 51 |
| |
53 | 52 |
| |
| |||
56 | 55 |
| |
57 | 56 |
| |
58 | 57 |
| |
59 |
| - | |
60 | 58 |
| |
61 | 59 |
| |
62 | 60 |
| |
| |||
127 | 125 |
| |
128 | 126 |
| |
129 | 127 |
| |
| 128 | + | |
| 129 | + | |
| 130 | + | |
| 131 | + | |
| 132 | + | |
130 | 133 |
| |
131 |
| - | |
132 |
| - | |
| 134 | + | |
| 135 | + | |
| 136 | + | |
133 | 137 |
| |
| 138 | + | |
| 139 | + | |
134 | 140 |
| |
135 |
| - | |
| 141 | + | |
136 | 142 |
| |
137 | 143 |
| |
138 | 144 |
| |
139 | 145 |
| |
140 | 146 |
| |
141 | 147 |
| |
| 148 | + | |
142 | 149 |
| |
143 | 150 |
| |
144 | 151 |
| |
| 152 | + | |
| 153 | + | |
| 154 | + | |
| 155 | + | |
| 156 | + | |
| 157 | + | |
| 158 | + | |
145 | 159 |
| |
146 | 160 |
| |
147 | 161 |
| |
|
0 commit comments
Comments
(0)