Skip to content

Commit 9a63078

Browse files
committed
Merge pull request git#47 from dscho/patch-2
rev_news ed. 2: fix rendering of underscore
2 parents b44ace4 + 7c8231f commit 9a63078

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

rev_news/draft/edition-2.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -121,11 +121,11 @@ becomes much faster to have as much information as possible in a
121121
single file. That's the purpose of the packed-ref file.
122122

123123
Peff discovered that one of his own commit that switched from fgets()
124-
to strbuf_getwholeline() to read the packed-ref file was in part
124+
to strbuf\_getwholeline() to read the packed-ref file was in part
125125
responsible for a big slowdown.
126126

127-
strbuf_getwholeline() is part of the Git strbuf API that is used for a
128-
lot of string related functions. And strbuf_getwholeline() used the
127+
strbuf\_getwholeline() is part of the Git strbuf API that is used for a
128+
lot of string related functions. And strbuf\_getwholeline() used the
129129
getc() function to get each character one by one until the end of each
130130
line, like this:
131131

@@ -138,7 +138,7 @@ while ((ch = getc(fp)) != EOF) {
138138
```
139139

140140
But it appears that it isn't very efficient. It is also problematic to
141-
use fgets() inside strbuf_getwholeline() as strbuf_getwholeline() is
141+
use fgets() inside strbuf\_getwholeline() as strbuf\_getwholeline() is
142142
used in some parts of the Git codebase to read lines that can contain
143143
the NUL character and fgets() would not read after the NUL. (And yeah
144144
working around that is not easy either.)

0 commit comments

Comments
 (0)