11$ rm go117
12
13▶TODO(prattmic): Ideally this would be built on the fly to better cover all
14executable formats, but then we need a network connection to download an old Go
15toolchain.
10 matches across 5 files for TODO lang:Markdown
13The current binary was built with "gcc version 14.2.0 (Debian 14.2.0-3+build4)".
14
15▶TODO(prattmic): Ideally this would be built on the fly to better cover all
16executable formats, but then we need to encode the intricacies of calling each
17platform's C compiler.
25
26should have a corresponding file named `doc/next/6-stdlib/99-minor/net/http/12345.md`.
27▶At a minimum, that file should contain either a full sentence or a TODO,
28ideally referring to a person with the responsibility to complete the note.
29
· · ·
36```
37If an accepted proposal is mentioned in a CL but not in the release notes, it will be
38▶flagged as a TODO by the automated tooling. That is true even for proposals that add API.
39
40Use the following forms in your markdown:
· · ·
59in `doc/next`.
60
61▶As a release cycle nears completion, run `relnote todo` to get a list of
62unfinished release note work.
63
127
128<!---
129▶TODO: can we come up with a shorter example that still shows the control flow?
130-->
131
· · ·
179
180<!---
181▶TODO: Probably explain here why the ordering of the passes matters, and why some
182passes like deadstore have multiple variants at different stages.
183-->
· · ·
222
223<!---
224▶TODO: need more ideas for this section
225-->
226
· · ·
242
243<!---
244▶TODO: more tips and info could likely go here
245-->
246
136
137#
138▶### TODO
139
140Add more relevant content.
Search syntax
auth login | both terms (AND is implicit) |
auth OR login | either term |
NOT path:vendor | exclude matches |
"exact phrase" | quoted exact match |
/func\s+Test/ | regex |
handler~1 | fuzzy (Levenshtein 1) |
file:*_test.go | filename glob |
path:pkg/auth/** | full path glob |
lang:go | language filter |