From: Grant Erickson <gerickson@nuovations.com>
To: connman@lists.linux.dev
Subject: [PATCH 0/3] connection: Rename 'connection.c' to 'gateway.c'
Date: Wed, 13 Dec 2023 11:59:58 -0800 [thread overview]
Message-ID: <20231213200001.1994492-1-gerickson@nuovations.com> (raw)
While historically, "connection.c" might have been a contextually-apt
name, today it might be better named "gateway.c" since its primary
focus is gateway routes and gateway route management.
Reflective of that, this renames "connection.c" to "gateway.c" and
updates public and private symbol names accordingly.
Grant Erickson (3):
connection: Rename 'connection.c' to 'gateway.c'.
gateway: Updated @file comment to reflect recent rename.
gateway: Rename public and private symbols after file rename.
Makefile.am | 2 +-
src/connman.h | 14 +++----
src/dnsproxy.c | 2 +-
src/{connection.c => gateway.c} | 65 ++++++++++++++++-----------------
src/inet.c | 2 +-
src/ipconfig.c | 8 ++--
src/main.c | 4 +-
src/network.c | 2 +-
src/provider.c | 4 +-
src/service.c | 22 +++++------
10 files changed, 62 insertions(+), 63 deletions(-)
rename src/{connection.c => gateway.c} (98%)
--
2.42.0
next reply other threads:[~2023-12-13 20:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 19:59 Grant Erickson [this message]
2023-12-13 19:59 ` [PATCH 1/3] connection: Rename 'connection.c' to 'gateway.c' Grant Erickson
2023-12-13 20:00 ` [PATCH 2/3] gateway: Updated @file comment to reflect recent rename Grant Erickson
2023-12-13 20:00 ` [PATCH 3/3] gateway: Rename public and private symbols after file rename Grant Erickson
2023-12-14 11:33 ` [PATCH 0/3] connection: Rename 'connection.c' to 'gateway.c' Marcel Holtmann
2023-12-19 13:32 ` Jussi Laakkonen
2023-12-20 5:53 ` Grant Erickson
2023-12-20 17:10 ` Jussi Laakkonen
2023-12-22 16:24 ` Grant Erickson
2024-01-02 11:57 ` Jussi Laakkonen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231213200001.1994492-1-gerickson@nuovations.com \
--to=gerickson@nuovations.com \
--cc=connman@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).