On Thu, Feb 05, 2026 at 09:32:29AM +0000, Egor Shestakov wrote: > Subject: git-describe in backport explanation > Hi everyone! > > I've just noticed that nobody is using `git describe` in backport > explanation. I suppose it may be convenient sometimes to mark certain > commit and version where a problem appears. Does this approach has some > drawbacks? I see only some awkwardness i.e. v2.6-dev1-142-g34527d535, > only "2.6" and "34527d535" are helpful for backporters, maybe "dev1" too, > but I'm not sure. Certainly this approach is not always applicable, > especially when a problem was made by many commits and it's unclean > what exactly is to blame for this. >
Hi Egor, 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. Regards, -- William Lallemand
