On 2020.11.25 14:08, Junio C Hamano wrote:
> Josh Steadmon <steadmon@xxxxxxxxxx> writes:
>
> > In order to more easily debug remote operations, it is useful to be able
> > to identify sessions on either side of the connection. This series
> > allows clients and servers to provide a unique session ID via a new
> > "session-id" protocol capability. This session ID can be logged on each
> > side of the connection, allowing logs to be joined during debugging
> > sessions.
> >
> > Changes from V2:
> > * De-emphasize connection to trace2
> > * Renamed capability from "trace2-sid" to "session-id"
> > * Noted (lack of) session ID structure in capability docs
> > * Advertise SID regardless of whether trace2 is enabled
> > * Simplify conditionals
> > * Style cleanups
> >
> > Changes since V1:
> > * Added a public trace2_session_id() function to trace2.{h,c}. Used this
> > in place of tr2_sid_get().
> > * Fixed a style issue regarding using NULL rather than 0.
>
> This round didn't see any responses, but it has already been
> extensively reviewed in the previous two rounds and looking good.
>
> Will mark to be merged to 'next', but please holler to stop me if
> needed (those in v2 review CC'ed).
>
> Thanks.
I still intend to write some documentation to clarify the trace2 SID
structure, but I think that can be done as a separate series. Thanks!
