Skip to content

RFC FIT documentation link vs copy

Sam Povilus u-boot 4 versions – In review

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v4 RFC Latest2 patches 2 repliesIn review
  2. v3 RFC2 patches 3 repliesSuperseded
  3. v2 RFC2 patches 1 replySuperseded
Earlier versions · 1
VersionPostedPatchesRepliesStatus
v1 RFC1 patch3 repliesSuperseded

Patches in v4 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2doc: Remove FIT documentation that is elsewheredoc/usage/fit/index.rst doc/usage/fit/source_file_format.rst+5 -6811 reply
2/2doc: add missing table of content linksdoc/usage/fit/index.rst+17 -41 reply

Reviews trailers per patch

All 2 patches have a Reviewed-by or Acked-by.

PatchSimon Glass
1/2R-b
2/2R-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v4 thread

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