#31957: automate upgrades
-------------------------------------------------+-------------------------
Reporter: anarcat | Owner: hiro
Type: project | Status:
| merge_ready
Priority: Medium | Milestone:
Component: Internal Services/Tor Sysadmin Team | Version:
Severity: Normal | Resolution:
Keywords: tpa-roadmap-february | Actual Points:
Parent ID: | Points: 0.5
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by anarcat):
> I thought it was easier to just reapply the patches cleanly. My plan
was to delete the old branches after merging, but since you have mentioned
I have now deleted the other branches.
i think it's fine to overwrite topic branches like this during the review
process. right now it means we lose the older version, but that's fine
because if I have cloned the repo, that branch is still technically
available locally (through the reflog). if we'd use gitlab for review, it
would be even visible through the web UI as well...
also, i think you forgot one branch (auto-updates) :)
thanks for the cleanup!
> Ok I'll try to merge this as see how it goes for chives.
excellent! don't forget about --noop ;) (now also `patn`)
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/31957#comment:18>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
[email protected]
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
