| Summary: | [PATCH] Please include "trash_folder" patch for mutt | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Adam Tkac <vonsch> | ||||
| Component: | mutt | Assignee: | Matej Mužila <mmuzila> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 20 | CC: | hhorak, mlichvar, mmuzila, obnox, ovasik, pertusus | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-06-30 00:44:18 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Adam Tkac
2013-11-05 15:10:47 UTC
Created attachment 819822 [details]
Proposed patch
Please note that I can push the patch & build new mutt myself if you are busy and you agree with inclusion of the patch.
Hi Adam, thank you for proposal. Currently the mutt upstream came back to live and because this patch seems interesting enough, I would first create a ticket in the mutt trac, write an email to dev mailing list and commit this change to the "default" branch (see http://www.mail-archive.com/mutt-dev@mutt.org/msg08865.html and https://bitbucket.org/mutt/mutt/branches). Please keep in mind, we're trying to be as much upstream compatible as possible and in this case, I'd rather saw the patch first in the mutt trac together with upstream response. I'll definitely check this issue in a few days after I receive an email from mutt-dev list. (In reply to jpacner from comment #2) > Hi Adam, thank you for proposal. Currently the mutt upstream came back to > live and because this patch seems interesting enough, I would first create a > ticket in the mutt trac, write an email to dev mailing list and commit this > change to the "default" branch (see > http://www.mail-archive.com/mutt-dev@mutt.org/msg08865.html and > https://bitbucket.org/mutt/mutt/branches). > > Please keep in mind, we're trying to be as much upstream compatible as > possible and in this case, I'd rather saw the patch first in the mutt trac > together with upstream response. I'll definitely check this issue in a few > days after I receive an email from mutt-dev list. Ok, sounds fine. Feel free to ask if you need more info from me. Have you already proposed the patch to upstream as I mentioned above? (In reply to jpacner from comment #4) > Have you already proposed the patch to upstream as I mentioned above? Ah, I didn't understand your comment #2, I thought you will propose it to upstream:) I will create the ticket and put reference here. I'm sorry for that. I'd be glad if you propose it to upstream :). Thank you! Reference for upstream ticket: http://dev.mutt.org/trac/ticket/3670 This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Since upstream said nothing about the patch, would it be possible to include it in the Fedora? For example Debian/Ubuntu already includes it... This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. I'd also appreciate the patch being included in the fedora package! This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |