Instead of having a timeline of a patch be global and sorted by timestamp, organise it via revisions. Each revision has an entry in the timeline, sorted by timestamp. Under each revision, a series of updates are inlined, also sorted by their timestamps. Currently, these updates can either be reviews or merges. For example: ``` ├────────────────────────────────────────────────────────────────────────────┤ │ ● opened by fintohaps (you) 1 week ago │ │ └── ✓ accepted by fintohaps (you) 1 week ago │ │ ↑ updated to 5f2a123e3f2aa60f2e03815df283563495b73085 (a1c3c0f) 1 week ago │ │ └── ✓ accepted by fintohaps (you) 1 week ago │ │ └── ✓ merged by cloudhead (z6Mkt67…v4N1tRk) now │ ╰────────────────────────────────────────────────────────────────────────────╯ ``` Signed-off-by: Fintan Halpenny <fintan.halpenny@gmail.com> X-Clacks-Overhead: GNU Terry Pratchett |
||
|---|---|---|
| .. | ||
| 1-new-project.md | ||
| 2-cloning.md | ||
| 3-issues.md | ||
| 4-patching-contributor.md | ||
| 5-patching-maintainer.md | ||
| 6-pulling-contributor.md | ||