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

RE: libcurl dependency for implementing RFC3161 timestamps

From
Randall S. Becker <rsbecker@nexbridge.com>
Date
Mar 9, 2016, 13:04 UTC
Message-ID
<001a01d17a04$2fb1bbd0$8f153370$@nexbridge.com>
In-Reply-To
<CACsJy8BNNQFP3LHxH06KewUjUVc1eox1mQPsg8b=acq-M=mHNQ@mail.gmail.com>
On March 9, 2016 6:41 AM, Duy Nguyen wrote:
Show 13 quoted lines
> To: Anton Wuerfel <anton.wuerfel@fau.de>
> Cc: Git Mailing List <git@vger.kernel.org>; i4passt@cs.fau.de;
> phillip.raffeck@fau.de
> Subject: Re: libcurl dependency for implementing RFC3161 timestamps
> 
> On Wed, Mar 9, 2016 at 6:24 PM, Anton Wuerfel <anton.wuerfel@fau.de>
> wrote:
> > -As git tag is a builtin part of the main git executable, introduce a
> > libcurl dependency for the main executable (maybe not best-practice).
> 
> libcurl was part of the main executable and then split out because it
> increased startup time [1]. I don't know if it's still true nowadays, maybe you
> should do a simple test before deciding to go that way.
The NSE NonStop port observed that at 2.7.3 (admittedly old) that libcurl was not used for local operations including status, log, reset, etc., but was needed for push, pull, fetch (a.k.a. network) operations. The libcurl.so is loaded statically at start-up for any components needing the latter operations. Added it for local processing is not going to help performance :(, which is quite bad enough on our platform.

Sincerely, Randall

-- Brief whoami: NonStop&UNIX developer since approximately UNIX(421664400)/NonStop(211288444200000000) -- In my real life, I talk too much.

Previous: Duy NguyenNext: Junio C Hamano
Message 3 of 4 in “libcurl dependency for implementing RFC3161 timestamps”
  1. Anton WuerfelMar 9, 2016
  2. Duy NguyenMar 9, 2016
  3. Randall S. BeckerMar 9, 2016
  4. Junio C HamanoMar 9, 2016

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.