git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Nathan Royce <nroycea+kernel@gmail.com>,  git@vger.kernel.org
Subject: Re: FR: Provide Out-Of-Tree Building; Provide Cross-Compile Parameters
Date: Mon, 08 Jul 2024 12:56:41 -0700	[thread overview]
Message-ID: <xmqqjzhvejye.fsf@gitster.g> (raw)
In-Reply-To: <CAPig+cTaH+TiD9Ut5Q_BPinqdAirW51J56R_tUTSnL=XGzxvfg@mail.gmail.com> (Eric Sunshine's message of "Mon, 8 Jul 2024 15:08:35 -0400")

Eric Sunshine <sunshine@sunshineco.com> writes:

>> I'd still suggest and prefer that git (and zlib) follows what others
>> have settled on doing to be cross-compile-friendly.
>
> I can't speak for the zlib project, but for this to happen in Git,
> someone with an interest in seeing such an outcome will need to submit
> patches.

Sure.  

Somebody unknown to the community suddenly coming here and
suggesting a feature alone would not achieve anything.  If there
were infinite engineering resources and motivated contributors, and
if sufficient number of contributors thought something is worth
doing, it would already have been done.  And "cross compilation" is
one of the things that is so obvious "isn't it nice if we had..."
items.  At least the offer has to be a bit more, like "I'll help in
this and that area (e.g., organizing the effort, keeping track of
progress, researching dependencies, ...).  Any others who want to
join forces?"

Thanks.






  reply	other threads:[~2024-07-08 19:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-08 16:37 FR: Provide Out-Of-Tree Building; Provide Cross-Compile Parameters Nathan Royce
2024-07-08 16:52 ` Eric Sunshine
2024-07-08 18:32   ` Nathan Royce
2024-07-08 19:08     ` Eric Sunshine
2024-07-08 19:56       ` Junio C Hamano [this message]
2024-07-10  3:20         ` Đoàn Trần Công Danh
2024-07-10  8:21           ` Nathan Royce
2024-07-10 15:53           ` 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=xmqqjzhvejye.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=nroycea+kernel@gmail.com \
    --cc=sunshine@sunshineco.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).