improve display of patch states
This commit is contained in:
parent
649543d9a7
commit
aeba6f21a4
18
README.md
18
README.md
|
@ -16,14 +16,26 @@
|
|||
* monorepo, with a main branch and others which are all cherry-picked from that (a full fork is necessary to deviate); restriction to just subsequences is good. (avoid accidental deviation)
|
||||
* snapshots (compressed "checkouts" basically, to avoid having to replay all of history on any complex actions) and patches (scripts, run in sandbox)
|
||||
* hooks, e.g. post-patch
|
||||
* patches can be in multiple states: "applied" (contained in main), "unreviewed" (not in main, active), "rejected/abandoned" (not in main, inactive)
|
||||
* patches can be in multiple states:
|
||||
* "applied" (contained in main)
|
||||
* "unreviewed" (not in main, active)
|
||||
* "rejected/abandoned" (not in main, inactive)
|
||||
|
||||
## features wanted on client side
|
||||
* patches can be in multiple states: "applied" (as above), "submitted" (pushed to server, but not applied), "unsubmitted" (not pushed to server)
|
||||
* patches can be in multiple states:
|
||||
* "applied" (as above)
|
||||
* "submitted" (pushed to server, but not applied)
|
||||
* "unsubmitted" (not pushed to server)
|
||||
* local tree can be in multiple states: "commited", "uncommited" (current state is not completely recorded in a commit)
|
||||
* no staging area, but using multiple trees should be easy
|
||||
* no "untracked" data, enforce proper use of `.ignore` files
|
||||
|
||||
## resulting design
|
||||
|
||||
tbd
|
||||
### patch states
|
||||
|
||||
* applied: contained in main
|
||||
* unreviewed: not in main, active
|
||||
* rejected/abandoned: not in main, inactive
|
||||
* submitted is equal to {unreviewed or abandoned}
|
||||
* unsubmitted
|
||||
|
|
Loading…
Reference in a new issue