From: Kousik Sanagavarapu <five231003@gmail.com>
To: git@vger.kernel.org
Cc: Kousik Sanagavarapu <five231003@gmail.com>
Subject: [RFC PATCH 0/3] pretty, builtin/mailinfo: don't rely on the_repository
Date: Tue, 15 Oct 2024 20:01:21 +0530 [thread overview]
Message-ID: <20241015144935.4059-1-five231003@gmail.com> (raw)
Hi,
Just a brief summary -
1/3 - the main changes are in environment.[ch] and repository.[ch], all
the others are just changes due to this change.
2/3 - the main changes are in pretty.[ch], all the other changes are due
to this change.
3/3 - This is pretty straight-forward.
One may notice that there are more "the_repository" occurences now than
before this change - which is good since it means that we have now made
the respective dependencies explicit (these were previously implicit).
The change in 1/3 is marked RFC since I was kind of skeptical about the
"repo" check in the repo_*() functions being done at _that_ level.
Since every other change in this series depends on this, I've marked all
the other RFC as well.
Thanks
Kousik Sanagavarapu (3):
repository: move git_*_encoding configs to repo scope
pretty: don't rely on "the_repository"
builtin/mailinfo: don't rely on "the_repository"
builtin/am.c | 6 +++--
builtin/blame.c | 2 +-
builtin/checkout.c | 6 +++--
builtin/commit.c | 8 +++---
builtin/log.c | 7 ++---
builtin/mailinfo.c | 5 ++--
builtin/merge.c | 2 +-
builtin/replay.c | 3 ++-
builtin/reset.c | 2 +-
builtin/rev-list.c | 4 +--
builtin/shortlog.c | 5 ++--
builtin/show-branch.c | 3 ++-
builtin/stash.c | 2 +-
bundle.c | 4 +--
commit.c | 9 ++++---
config.c | 10 ++++---
environment.c | 13 ---------
environment.h | 6 -----
log-tree.c | 6 ++---
pretty.c | 63 ++++++++++++++++++++++++-------------------
pretty.h | 14 +++++-----
range-diff.c | 2 +-
remote-curl.c | 4 ++-
repository.c | 13 +++++++++
repository.h | 6 +++++
revision.c | 16 +++++------
sequencer.c | 28 ++++++++++---------
submodule.c | 2 +-
28 files changed, 139 insertions(+), 112 deletions(-)
--
2.47.0.73.g7a80afd5fd.dirty
next reply other threads:[~2024-10-15 14:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 14:31 Kousik Sanagavarapu [this message]
2024-10-15 14:31 ` [PATCH 1/3] repository: move git_*_encoding configs to repo scope Kousik Sanagavarapu
2024-10-15 16:05 ` shejialuo
2024-10-16 6:15 ` Patrick Steinhardt
2024-10-16 17:24 ` Kousik Sanagavarapu
2024-10-17 5:03 ` Patrick Steinhardt
2024-10-17 13:06 ` shejialuo
2024-10-16 16:31 ` Kousik Sanagavarapu
2024-10-15 14:31 ` [PATCH 2/3] pretty: don't rely on "the_repository" Kousik Sanagavarapu
2024-10-15 14:31 ` [PATCH 3/3] builtin/mailinfo: " Kousik Sanagavarapu
2024-10-15 16:14 ` shejialuo
2024-10-15 19:51 ` [RFC PATCH 0/3] pretty, builtin/mailinfo: don't rely on the_repository Taylor Blau
2024-10-16 17:49 ` Kousik Sanagavarapu
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=20241015144935.4059-1-five231003@gmail.com \
--to=five231003@gmail.com \
--cc=git@vger.kernel.org \
/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 NNTP newsgroup(s).