From: Linus Arver <linus@ucla.edu>
To: Junio C Hamano <gitster@pobox.com>,
Linus Arver via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Christian Couder <chriscool@tuxfamily.org>
Subject: Re: [PATCH] trailer: spread usage of "trailer_block" language
Date: Tue, 12 Nov 2024 02:49:13 -0800 [thread overview]
Message-ID: <CAMo6p=GOjmUQWHE9QH0wUY=FCzN4-mjknryWRbp4dQW4MFthqw@mail.gmail.com> (raw)
In-Reply-To: <xmqq34jx8adx.fsf@gitster.g>
Junio C Hamano <gitster@pobox.com> writes:
> "Linus Arver via GitGitGadget" <gitgitgadget@gmail.com> writes:
>
>> From: Linus Arver <linusa@google.com>
>>
>> Deprecate the "trailer_info" struct name and replace it with
>> "trailer_block". This is more readable, for two reasons:
>>
>> 1. "trailer_info" on the surface sounds like it's about a single
>> trailer when in reality it is a collection of one or more trailers,
>> and
>>
>> 2. the "*_block" suffix is more informative than "*_info", because it
>> describes a block (or region) of contiguous text which has trailers
>> in it, which has been parsed into the trailer_block structure.
>>
>> Rename the
>>
>> size_t trailer_block_start, trailer_block_end;
>>
>> members of trailer_info to just "start" and "end". Rename the "info"
>> pointer to "trailer_block" because it is more descriptive. Update
>> comments accordingly.
>
> All makes sense. Often "_info" suffix has very low information
> density, as everything is "info" in a sense ;-)
Exactly.
> Will merge to 'next' (unless there is a belated "it may not break,
> but it is not a good idea because ...", that is).
Yup, sounds good. Thanks!
prev parent reply other threads:[~2024-11-12 10:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-13 11:58 [PATCH] trailer: spread usage of "trailer_block" language Linus Arver via GitGitGadget
2024-10-15 11:32 ` Linus Arver
2024-10-15 19:47 ` Taylor Blau
2024-11-05 21:02 ` Johannes Schindelin
2024-11-12 10:39 ` Linus Arver
2024-11-12 2:16 ` Junio C Hamano
2024-11-12 10:49 ` Linus Arver [this message]
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='CAMo6p=GOjmUQWHE9QH0wUY=FCzN4-mjknryWRbp4dQW4MFthqw@mail.gmail.com' \
--to=linus@ucla.edu \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.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).