Hi -
> > I think it has a chance to be useful to other clients too, for example
> > for other proxy / authentication schemes. And given that there is a
> > shared library boundary, private APIs aren't in easy reach.
> > "separately" as in separate commits? ... I suppose, if it really
> > matters.
Hi Frank,
On Tue, 2020-02-25 at 10:32 -0500, Frank Ch. Eigler wrote:
> > > +/* Add an outgoing HTTP request "Header: Value". Copies string. */
> > > +int debuginfod_add_http_header (debuginfod_client *client, const char*
> > > header);
> >
> > This one seems different from the others and has
Hi -
> > This latter is a bit long and should probably be abbreviated, wdyt?
>
> Might want to abbrev the build-id part to /81..aa/. The interesting
> part is which server is used imho.
Yeah, OK.
> > +/* Add an outgoing HTTP request "Header: Value". Copies string. */
> > +int debuginfod_add_
Hi Frank,
On Mon, 2020-02-24 at 22:35 -0500, Frank Ch. Eigler wrote:
> As a part of PR25369, I propose this small set of client api
> extensions, requested by gdb developers and needed by personal
> experience. (I plan to roll it out on my debuginfod servers shortly
> to let it soak.) An end-use
On 2020-02-24 10:35 p.m., Frank Ch. Eigler wrote:
> Hi -
>
> As a part of PR25369, I propose this small set of client api
> extensions, requested by gdb developers and needed by personal
> experience. (I plan to roll it out on my debuginfod servers shortly
> to let it soak.) An end-user visible
Hi -
As a part of PR25369, I propose this small set of client api
extensions, requested by gdb developers and needed by personal
experience. (I plan to roll it out on my debuginfod servers shortly
to let it soak.) An end-user visible immediate difference is in the
DEBUGINFOD_PROGRESS=1 format me
