From: Md Isfarul Haque <isfarul.876@gmail.com>
To: Christian Couder <christian.couder@gmail.com>,
Md Isfarul Haque via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] FIX: use utf8_strnwidth for line_prefix in diff.c
Date: Thu, 25 Jan 2024 11:12:02 +0530 [thread overview]
Message-ID: <d135a291-7b51-4cd6-86ec-676c1c5b04e9@gmail.com> (raw)
In-Reply-To: <CAP8UFD2oxpefhGtH61wZvcHEvd24jtu_ZBVsnNZMjD2aM_NDcg@mail.gmail.com>
On 1/25/24 01:31, Christian Couder wrote:
> On Wed, Jan 24, 2024 at 3:04 PM Md Isfarul Haque via GitGitGadget
> <gitgitgadget@gmail.com> wrote:
>>
>> From: Md Isfarul Haque <isfarul.876@gmail.com>
>>
>> This patch adresses diff.c:2721 and proposes the fix using a new function.
>
> Please give more details here about what is currently at diff.c:2721
> and what the patch is fixing, as lines at diff.c:2721 could move to a
> different location if some changes are made to diff.c before your
> patches get merged or after they get merged.
>
> Also if the patch is addressing an issue in a code comment I would
> expect the corresponding code comment to be removed by the patch.
I understand and apologize for the mess-up. I will keep it in mind next time.
> About the subject, maybe "diff: use utf8_strnwidth() for line_prefix"
> is already better.
>
>> Signed-off-by: Md Isfarul Haque <isfarul.876@gmail.com>
>> ---
>> diff.c | 18 ++++++++++++++++--
>> diff.h | 1 +
>> 2 files changed, 17 insertions(+), 2 deletions(-)
>>
>> diff --git a/diff.c b/diff.c
>> index a89a6a6128a..e3223b8ce5b 100644
>> --- a/diff.c
>> +++ b/diff.c
>> @@ -2300,6 +2300,20 @@ const char *diff_line_prefix(struct diff_options *opt)
>> return msgbuf->buf;
>> }
>>
>> +const struct strbuf *diff_line_prefix_buf(struct diff_options *opt)
>
> This function seems to be used only in diff.c, so it could be static.
As Junio pointed out, I will probably use the existing function with slight
modifications and use it. Besides, having unnecessary allocations and frees
will probably only add overhead.
--
Thanks and regards
Md. Isfarul Haque
next prev parent reply other threads:[~2024-01-25 5:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 14:04 [PATCH 0/2] [GSoC][RFC/Patch] FIX: use utf8_strnwidth for line_prefix in diff.c Md Isfarul Haque via GitGitGadget
2024-01-24 14:04 ` [PATCH 1/2] " Md Isfarul Haque via GitGitGadget
2024-01-24 20:01 ` Christian Couder
2024-01-25 5:42 ` Md Isfarul Haque [this message]
2024-01-24 20:08 ` Junio C Hamano
2024-01-25 5:52 ` Md Isfarul Haque
2024-01-24 14:04 ` [PATCH 2/2] FIX memory leak in one branch Md Isfarul Haque via GitGitGadget
2024-01-24 20:11 ` Junio C Hamano
2024-01-24 17:42 ` [PATCH 0/2] [GSoC][RFC/Patch] FIX: use utf8_strnwidth for line_prefix in diff.c Junio C Hamano
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=d135a291-7b51-4cd6-86ec-676c1c5b04e9@gmail.com \
--to=isfarul.876@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
/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).