| commit | 560bdb37cc57a9421b6e9f7d4c11f0b03659b562 | [log] [tgz] |
|---|---|---|
| author | Harald Welte <laforge@osmocom.org> | Fri Dec 04 22:24:47 2020 +0100 |
| committer | Harald Welte <laforge@osmocom.org> | Sat Dec 05 12:06:42 2020 +0100 |
| tree | 91a606d92b98b77afc121ccc1abefada60740c84 | |
| parent | 173a182d031db9097651cde16d81293c566392c2 [diff] |
gb_proxy: Rename gbproxy_peer to gbproxy_bvc I cannot really read the code while it contains its historical weird naming. A "peer" used to be a strange amalgamation of NSE + BVC, while in reality we can have any number of BVC on top of each NSE. We recently started to split the peer into a gbproxy_nse_peer + gbproxy_peer. This takes it one step further and renames gbproxy_peer to gbproxy_bvc, as that's really what it is. Change-Id: Iae01067282a6401f6af4cab731202872d2cdb080