Hello Daniel

sorry about the delay, just one question
the changes you made about this issue, are all ot these

commit c7e228eae76a432ea93fac7e95f50fe50979d79e
Author: Daniel-Constantin Mierla <miconda@gmail.com>
Date:   Fri Mar 31 18:34:00 2023 +0200

    pua: updates for the new t field names

commit c321f28ff657c921b8de2b84e66908f281d35d78
Author: Daniel-Constantin Mierla <miconda@gmail.com>
Date:   Fri Mar 31 18:22:23 2023 +0200

    tm: use header attribute shortcuts to match inside t_lookup_callid()

commit 2bd1227b2440dd376c18e6c964f569e0e9ba4730
Author: Daniel-Constantin Mierla <miconda@gmail.com>
Date:   Fri Mar 31 15:18:13 2023 +0200

    tm: keep shortcut the cseq header method

commit 734fd2910cd437205da870ad1e329eaefe2f043a
Author: Daniel-Constantin Mierla <miconda@gmail.com>
Date:   Fri Mar 31 08:05:10 2023 +0200

    sca: updates for the new t field names

commit ecd906dabbc5dc19d0fabb35d22320e2ba3fccf0
Author: Daniel-Constantin Mierla <miconda@gmail.com>
Date:   Fri Mar 31 08:04:59 2023 +0200

    lcr: updates for the new t field names

commit 8f39d0ff741a3ba5819c6c0f96b8f575d30ab770
Author: Daniel-Constantin Mierla <miconda@gmail.com>
Date:   Fri Mar 31 08:04:43 2023 +0200

    keepalive: updates for the new t field names

commit 927a2451e084e886d2548fdae3f5f4cd3abd0a4b
Author: Daniel-Constantin Mierla <miconda@gmail.com>
Date:   Fri Mar 31 08:04:11 2023 +0200

    dispatcher: updates for the new t field names

commit 8d69c0d68347198ccaea57a8ac4eeb040d19287a
Author: Daniel-Constantin Mierla <miconda@gmail.com>
Date:   Fri Mar 31 08:02:10 2023 +0200

    tm: rename shortcuts to from/to/callid/cseq headers
    
    - reflect better that they are with header names
    - new fields to point to callid value and cseq number to facilitate use
      of them directly without new parsing or printing with header names

?
Apart of testing directly on master branch, if I tested on 5.4 for instance, should I cherry pick all of them? (asuming there are no conflicts)
thanks a lot and regards
david


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <kamailio/kamailio/pull/3393/c1565263719@github.com>