From: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
To: "Torsten Bögershausen" <tboegi@web.de>, rsbecker@nexbridge.com
Cc: "Eric Sunshine" <sunshine@sunshineco.com>,
"Alejandro R. Sedeño" <asedeno@mit.edu>,
"Taylor Blau" <me@ttaylorr.com>,
git@vger.kernel.org, sandals@crustytoothpaste.net,
asedeno@google.com
Subject: Re: [PATCH 0/2] Restore support for older libcurl and fix some typos
Date: Thu, 17 Oct 2024 11:15:08 +0200 [thread overview]
Message-ID: <ZxDVnGigNP4UUG3a@ugly> (raw)
In-Reply-To: <20241017065936.GA16141@tb-raspi4>
On Thu, Oct 17, 2024 at 08:59:37AM +0200, Torsten Bögershausen wrote:
>Maintaining production software and hardware, systems using specialized
>hardware with Linux drivers dependend on the Linux kernel is daily
>work.
>
yes.
>And here tools like Git are needed (and appreciated).
>
but why?
why do you need bleeding edge git on these special-purpose systems from
the stone age? wouldn't any sane developer (cross-)build on a modern
system (which usually has about an order of magnitude more computing
power, aside from the newer tools) and then deploy and extract only
what's needed via some mostly automated process? it would only matter if
git was part of the production software (what for?), but then we're back
to square one.
next prev parent reply other threads:[~2024-10-17 9:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 13:13 [PATCH 0/2] Restore support for older libcurl and fix some typos Alejandro R. Sedeño
2024-10-14 13:13 ` [PATCH 1/2] Conditional use of CURLOPT_PROXYHEADER based on libcurl version Alejandro R. Sedeño
2024-10-14 13:13 ` [PATCH 2/2] Fix inconsistencies in git-curl-compat.h Alejandro R. Sedeño
2024-10-15 0:28 ` [PATCH 0/2] Restore support for older libcurl and fix some typos Taylor Blau
2024-10-15 0:51 ` Alejandro R. Sedeño
2024-10-15 6:29 ` Eric Sunshine
2024-10-15 19:22 ` Taylor Blau
2024-10-17 6:59 ` Torsten Bögershausen
2024-10-17 9:15 ` Oswald Buddenhagen [this message]
2024-10-17 9:30 ` Torsten Bögershausen
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=ZxDVnGigNP4UUG3a@ugly \
--to=oswald.buddenhagen@gmx.de \
--cc=asedeno@google.com \
--cc=asedeno@mit.edu \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=rsbecker@nexbridge.com \
--cc=sandals@crustytoothpaste.net \
--cc=sunshine@sunshineco.com \
--cc=tboegi@web.de \
/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).