From: Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>
To: git@vger.kernel.org
Cc: Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>
Subject: [GSoC][RFC PATCH 3/6] revision: add subject_extra_field to struct rev_info
Date: Mon, 3 Mar 2025 19:00:26 -0300 [thread overview]
Message-ID: <20250303220029.10716-4-lucasseikioshiro@gmail.com> (raw)
In-Reply-To: <20250303220029.10716-1-lucasseikioshiro@gmail.com>
Currently, the `struct rev_info` is responsible for holding information
about the prefix that is added at the beginning of the subject when
`format-patch` is called. This way, it makes sense that it also holds
the information of the extra prefix, if it is present.
Add a new field called `subject_extra_field` to `struct rev_info` and
use NULL as its default value.
Signed-off-by: Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>
---
revision.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/revision.h b/revision.h
index 71e984c452..70927ef1fb 100644
--- a/revision.h
+++ b/revision.h
@@ -294,6 +294,7 @@ struct rev_info {
const char *extra_headers;
const char *log_reencode;
const char *subject_prefix;
+ const char *subject_extra_prefix;
int patch_name_max;
int no_inline;
int show_log_size;
@@ -413,6 +414,7 @@ struct rev_info {
.expand_tabs_in_log = -1, \
.commit_format = CMIT_FMT_DEFAULT, \
.expand_tabs_in_log_default = 8, \
+ .subject_extra_prefix = NULL, \
}
/**
--
2.39.5 (Apple Git-154)
next prev parent reply other threads:[~2025-03-03 22:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 22:00 [GSoC][RFC PATCH 0/6] Add --subject-extra-prefix flag to format-patch Lucas Seiki Oshiro
2025-03-03 22:00 ` [GSoC][RFC PATCH 1/6] builtin/log: add subject-extra-prefix " Lucas Seiki Oshiro
2025-03-03 22:00 ` [GSoC][RFC PATCH 2/6] builtin/log: die if -k and --suject-extra-prefix are used together Lucas Seiki Oshiro
2025-03-03 22:36 ` Eric Sunshine
2025-03-03 22:00 ` Lucas Seiki Oshiro [this message]
2025-03-03 22:00 ` [GSoC][RFC PATCH 4/6] builtin/log: fill subject extra prefix in format-patch Lucas Seiki Oshiro
2025-03-03 22:00 ` [GSoC][RFC PATCH 5/6] log-tree: add subject prefix in output email subject Lucas Seiki Oshiro
2025-03-03 22:00 ` [GSoC][RFC PATCH 6/6] t4014: add tests for the new flag --subject-extra-prefix Lucas Seiki Oshiro
2025-03-03 23:08 ` [GSoC][RFC PATCH 0/6] Add --subject-extra-prefix flag to format-patch Junio C Hamano
2025-03-04 7:32 ` Patrick Steinhardt
2025-03-04 22:06 ` Junio C Hamano
2025-03-04 13:05 ` Junio C Hamano
2025-03-04 23:19 ` Lucas Seiki Oshiro
2025-03-05 2:06 ` Junio C Hamano
2025-03-05 14:26 ` Lucas Seiki Oshiro
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=20250303220029.10716-4-lucasseikioshiro@gmail.com \
--to=lucasseikioshiro@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).