Decision: seeking a memo from its transcript #6
No reviewers
Labels
No labels
area/agent
area/capture
area/editor
area/geo
area/security
area/sync
area/transcription
area/ui
area/vault
area/voice-memos
blocked
milestone/M1
milestone/M2
milestone/M3
milestone/M4
needs-decision
needs-hardware
p0
p1
p2
type/bug
type/enhancement
type/feature
type/idea
type/infrastructure
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Stash/stash-docs!6
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "m2-03-transcript-seek-decision"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The decision file behind stash-ios#44 (M2-03).
This branch carries five earlier decision files as well as mine.
mainhere has only theinitial commit — the decisions for the documents directory, the Record control, the unfinalised
tail, the two readers, and the audio session were committed locally on a branch called
m1-13-control-decisionand never pushed. They are ancestors of my commit, so they arrive withit. Flagging rather than quietly shipping six commits under one title; say if you would rather
they went separately.
Mine records why the cue under the playhead is the last one that started rather than the one
whose range contains it, why file order is preserved for reading while a sorted copy answers the
time lookup, why following is abandoned on interaction and resumed only by asking, and why cue
text lost its selectability. It also records the measurement: a one-hour memo seeking from cues
near the end landed within about half a second of the words.
84df485de9tobbf29d4adeView command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.