Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #29905

Closed (moved)
Open
Opened Mar 26, 2019 by George Kadianakis@asn

git-maintainance-scripts: merge-forward should provide indications of merges actually occuring

I'd like the merge-forward script (see #29391 (moved)) to highlight me the merge-forwards that actually merged something, contrary to the ones that were NOPs.

My fear is that I will have left some garbage in my worktrees and a merge-forward will merge forward something that I have not anticipated (e.g. from 035 to 040, when I just wanted to merge-fwd from 040 to master).

This has not yet happened, but I'd like as much protection as possible when using these automatic tools :)

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#29905