From: <rsbecker@nexbridge.com>
To: "'Todd Zullinger'" <tmz@pobox.com>
Cc: <git@vger.kernel.org>
Subject: RE: [ANNOUNCE] Git v2.41.0-rc2
Date: Thu, 25 May 2023 13:48:52 -0400 [thread overview]
Message-ID: <027f01d98f31$2e94e660$8bbeb320$@nexbridge.com> (raw)
In-Reply-To: <ZG-dXsQpLrAoNVSD@pobox.com>
On Thursday, May 25, 2023 1:40 PM, Todd Zullinger wrote:
>rsbecker@nexbridge.com wrote:
>> On Thursday, May 25, 2023 12:39 PM, Todd Zullinger wrote:
>>> I don't used the option, as the systems I build for have tcl/tk, but
>>> I don't see where setting that would have an effect on .po files
>>> (apart from those in git-gui or gitk-git, of course).
>>
>> Those two are where the .po are unprocessed.
>
>I guess I don't understand the issue then. If you don't have tcl/tk, then
what's the
>problem with not having the po files processed for these apps you cannot
run?
>
>What errors does this cause? I'm not really an expert in this area, but I
imagine a
>more concrete explanation of the problem might be helpful.
What I'm concerned about is what other users of the builds are depending on.
If I change a setting in config.mak.uname to just remove a message that has
no otherwise impact, I am fine with doing that. Adding NO_TCLTK has a
broader impact on the overall build, so I am hesitant to put my name on a
contribution (trivial regardless) for such a change without understanding
why there is a non-trivial impact. My thought as this point, as a packager,
is that I should live with the situation.
prev parent reply other threads:[~2023-05-25 17:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 21:41 [ANNOUNCE] Git v2.41.0-rc2 Junio C Hamano
2023-05-24 23:06 ` rsbecker
2023-05-24 23:40 ` Todd Zullinger
2023-05-25 13:56 ` rsbecker
2023-05-25 14:48 ` rsbecker
2023-05-25 16:38 ` 'Todd Zullinger'
2023-05-25 17:26 ` rsbecker
2023-05-25 17:39 ` 'Todd Zullinger'
2023-05-25 17:48 ` rsbecker [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='027f01d98f31$2e94e660$8bbeb320$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=tmz@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 read-only IMAP folder(s) and NNTP newsgroup(s).