Fold common_py3 back into common #3456
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#3456
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Pursuant to https://github.com/tahoe-lafs/tahoe-lafs/pull/823/files#r494347203 ff.
Reviewing the history of common_py3.py, here is a list of commits to undo:
a758f32edf
) (common)416ab64335
)This isn't simply a revert, however, since the classes have changed since being moved into common_py3. It's the current version of each class that we want to move back. Also, they came from different sources (common, common_util, etc.) and I plan to move them each back where they came from—so this isn't a simple copy/paste into common.py.
(https://github.com/tahoe-lafs/tahoe-lafs/pull/842)
The PR was merged in https://github.com/tahoe-lafs/tahoe-lafs/commit/2fe2acf4c72d5921d92ed7474bfd92565c136c8a