Merge upstream
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- c
- Domain
- operating-systems
Research direction
Start by reviewing the existing patches referenced in the issue and checking their upstream status. Clarify with the maintainers which changes should be accepted upstream and how Mint should receive new Mint major versions and PackageKit security updates; done means the scope and upstream path are agreed.
Written by the indexing model from the issue text.
Description
Hi, @clefebvre @mtwebster have you tried to add your patch upstream?
I think it would be good to improve the sw, make you waste less time to keep rebasing it and make mint upload every new major version of mint and new security update of packagekit
- Dominant language
- C
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
level/task module/gcp type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
hapostgres/pg_auto_failover#1190 ·
-
docs
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
P3 sonic-vpp
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sonic-net/sonic-buildimage#29662 ·