Hi William! On Thu, Feb 05, 2026 at 11:25:01AM +0100, William Lallemand wrote: > > I'm not sure what you mean, most of the time we are just specifying in which > branches the patch need to be backported. (3.3, 3.2, 3.1 etc.) > > When a bug is more complex and need a more descriptive analyze we use the > commit ID and the subject to describe commit that we refer to. But having the > whole `git describe` for that is not really useful.
You understood me right, thanks for explanation. I suppose that output from `git describe` can be more homogenous and points to the mistake in all cases. I thought that it may be convenient when I did my last contribution. > Subject: [PATCH 1/2] BUG/MINOR: startup: fix allocation error message of > progname string > > Initially when init_early was introduced the progname string was a local > used for temporary storage of log_tag. Now it's global and detached from > log_tag enough. Thus, in the past we could inform that log_tag > allocation has been failed but not now. > > Must be backported since the progname string became global, that is > v3.1-dev9-96-g49772c55e Cheers! -- Egor Shestakov egor ascii(0x40) ved1 ascii(0x2E) me
