[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <e5419ba84c64e9146652864072b1941ef310de4f.camel@gmail.com>
Date: Tue, 25 Nov 2025 21:30:24 +0530
From: ally heev <allyheev@...il.com>
To: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
Cc: Krzysztof Kozlowski <krzk@...nel.org>, Miri Korenblit
<miriam.rachel.korenblit@...el.com>, linux-wireless@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH RESEND iwlwifi-next] wifi: iwlwifi: mld: remove unused
variable in d3.c
On Tue, 2025-11-25 at 08:54 -0500, Konstantin Ryabitsev wrote:
> On Tue, Nov 25, 2025 at 12:50:44PM +0530, ally heev wrote:
> > > > Yes, I use b4 for my patches. I work on other open source projects
> > > > which use Github. So, my global git config commit autosign is set to
> >
> > typo: `tag autosign`
> >
> > > > `true`, hence you have seen PGP signatures.
> > >
> > > Interesting! I've not seen this cause PGP signatures to be added to "git show"
> > > output before. I've tried to replicate it locally, but even if I have a signed
> > > git commit, I can't make the "gpgsig" header to show up in the output of "git
> > > show --format=email" (which is what b4 uses). Do you have some local git
> > > configuration changes that make "gpgsig" fields show up in the output of "git
> > > show"?
> > >
> > > -K
> >
> > I think b4 uses tags for patch series. I have checked old
> > patches(before disabling autosign) and found that signature is only
> > added on first(cover-letter) of the patch series
>
> Oh! Interesting, so this happened on resend? I'll test it out, thanks!
I didn't get it. Signature was added to every cover-letter of patch
series before I disabled `tag autosign`
>
> -K
Powered by blists - more mailing lists