Thanks Daniel @miconda
Understand. Sure i will use commit permission only for rpm/alpine/docker
packaging.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Merged #1715 into master.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/1715#event-1965454893___
Kamailio (SER) - Development Mailing
I am going to merge and also grant you commit access, so you can commit to the
RPM specs directly and backport as needed (you can still do pull request if you
want others to review -- for commits to other parts than RPM specs, keep doing
pull requests so the main developer for that part has a
@henningw this two commits also need on `5.2` branch.
Reference to #1711 is made to prevent merge conflict on cherry-pick.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Backport of the three commits in 5.2 done.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/1715#issuecomment-437315768___
Kamailio (SER) -
Could you also backport https://github.com/kamailio/kamailio/pull/1711 into
`5.2` branch.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Pre-Submission Checklist
- [x] Commit message has the format required by CONTRIBUTING guide
- [ ] Commits are split per component (core, individual modules, libs, utils,
...)
- [ ] Each component has a single commit (if not, squash them into one commit)
- [x] No commits to README files for
