RFC FIT documentation link vs copy
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v4 RFC Latest2 patches 2 repliesIn review
- v3 RFC2 patches 3 repliesSuperseded
- v2 RFC2 patches 1 replySuperseded
Earlier versions · 1
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v1 RFC | 1 patch | 3 replies | Superseded |
Patches in v4 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | doc: Remove FIT documentation that is elsewheredoc/ doc/ | +5 | 1 reply | |
| 2/2 | doc: add missing table of content linksdoc/ | +17 | 1 reply |
Reviews trailers per patch
All 2 patches have a Reviewed-by or Acked-by.
| Patch | Simon Glass |
|---|---|
| 1/2 | R-b |
| 2/2 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [RFC v4 0/2] FIT documentation link vs copy
I'm proposing linking the FIT documentation instead of double book keeping it, it does have the disadvantage of making it more difficult to see the documentation especially if offline.
v2: update table of contents instead of removing
v3: remove duplicate entries, provide commit message
v4: cleanup: newlines, duplicated word, commit order
Sam Povilus (2):
doc: Remove FIT documentation that is elsewhere
doc: add missing table of content links
doc/usage/fit/index.rst | 25 +- doc/usage/fit/source_file_format.rst | 682 +-------------------------- 2 files changed, 22 insertions(+), 685 deletions(-)
Signature · 1 line
2.34.1