git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 0/2] Restore support for older libcurl and fix some typos

From
Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
Date
Oct 17, 2024, 09:15 UTC
Message-ID
<ZxDVnGigNP4UUG3a@ugly>
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.

Previous: Torsten BögershausenNext: Torsten Bögershausen
Message 9 of 10 in “Restore support for older libcurl and fix some typos”
  1. 0/2 Restore support for older libcurl and fix some typosAlejandro R. Sedeño, Oct 14, 2024
  2. 1/2 Conditional use of CURLOPT_PROXYHEADER based on libcurl versionAlejandro R. Sedeño, Oct 14, 2024
  3. 2/2 Fix inconsistencies in git-curl-compat.hAlejandro R. Sedeño, Oct 14, 2024
  4. Taylor BlauOct 15, 2024
  5. Alejandro R. SedeñoOct 15, 2024
  6. Eric SunshineOct 15, 2024
  7. Taylor BlauOct 15, 2024
  8. Torsten BögershausenOct 17, 2024
  9. Oswald BuddenhagenOct 17, 2024
  10. Torsten BögershausenOct 17, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.