Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • M mw
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 18
    • Issues 18
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • milliways
  • mw
  • Issues
  • #28
Closed
Open
Created Oct 12, 2017 by Andrew Price@welshbyteMaintainer

New user-friendly version of '.replay since'

.replay since takes a Unix epoch timestamp which isn't very intuitive to use when exposed directly to users.

The client should accept a new .replay ... invocation that takes human-readable timestamps, convert them to Unix timestamps and then send the appropriate since command to the server.

For some inspiration, see the Parsing Timestamps section of systemd.time(7) and the corresponding implementation.

Assignee
Assign to
Time tracking