Re: Pull-request related question.
On Sat, Nov 12, 2022 at 08:29:17PM -, Sergey Mende wrote: > Hi, > during development of my own project I hit the bug in `gdb` that is already > fixed upstream but not backported to rawhide yet. > I did a backport and ready to submit a PR. What is the right way to proceed: > > a) just file a PR; > b) open a bug in bugzilla, submit a PR; > c) submit a PR, open a bug in bugzilla noting that PR is in a way? There's no hard rule or even good convention here, but I would personally say just a PR and waiting a bit would be best. If there's no answer after a while, a bug could be filed to attract the maintainers(s) attention. kevin signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Pull-request related question.
Thank you, Scott. Regards, Sergey On Sun, Nov 13, 2022 at 6:04 AM Scott Talbert wrote: > On Sat, 12 Nov 2022, Sergey Mende wrote: > > > Hi, > > during development of my own project I hit the bug in `gdb` that is > already fixed upstream but not backported to rawhide yet. > > I did a backport and ready to submit a PR. What is the right way to > proceed: > > > > a) just file a PR; > > b) open a bug in bugzilla, submit a PR; > > c) submit a PR, open a bug in bugzilla noting that PR is in a way? > > It looks like the gdb maintainer(s) are relatively responsive to PRs, so > you could probably just open a PR. > > Scott > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Pull-request related question.
On Sat, 12 Nov 2022, Sergey Mende wrote: Hi, during development of my own project I hit the bug in `gdb` that is already fixed upstream but not backported to rawhide yet. I did a backport and ready to submit a PR. What is the right way to proceed: a) just file a PR; b) open a bug in bugzilla, submit a PR; c) submit a PR, open a bug in bugzilla noting that PR is in a way? It looks like the gdb maintainer(s) are relatively responsive to PRs, so you could probably just open a PR. Scott ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
