On Tue, Apr 23, 2024 at 03:08:05PM +0200, Théo Lebrun wrote: > Hello, > > On Tue Apr 23, 2024 at 12:25 PM CEST, Krzysztof Kozlowski wrote: > > On 23/04/2024 12:04, Théo Lebrun wrote: > > > Hello, > > > > > > On Tue Apr 23, 2024 at 7:00 AM CEST, Mark Brown wrote: > > >> On Mon, Apr 22, 2024 at 06:52:47PM +0200, Théo Lebrun wrote: > > >>> All commits tagged "(no commit info)" do not show up in your for-next > > >>> branch. Is that expected and is there anything I can do? There was one > > >>> pending -Wunused-variable compiler warning to be addressed for > > >>> example, see [0]. > > >> > > >> Please submit any patches you'd like to see included. If there were > > >> outstanding issues that need fixing then fixing those prior to > > >> submitting would be sensible. > > > > > > Seeing "Applied" followed by a list of commits, with some of those not > > > being applied confused me. > > > > That's a standard output of b4 and maybe also Patchwork, if some parts > > are applied. > > Thanks for the pointer. I've created an issue over at b4 to see what > people think about this matter. Current behavior is not intuitive as a > young contributor. FWIW, given I see `having a more confident comment such as "(commit not applied)".` there, having (no commit info) doesn't mean that it wasn't applied always. Sometimes I've found that due to changes in the patch b4 could not detect that it was applied and reported (no commit info).
Attachment:
signature.asc
Description: PGP signature
