On Fri, Feb 07, 2025 at 07:27:43AM +0100, Michal Simek wrote:
> 
> 
> On 2/7/25 00:33, Tom Rini wrote:
> > On Thu, Feb 06, 2025 at 08:57:41AM +0100, Michal Simek wrote:
> > 
> > > Hi Tom,
> > > 
> > > please pull these patches to your tree. Nothing really significant there.
> > > Some binman fixes which were not spot before and switching our platform to
> > > LWIP to have cover it better.
> > > 
> > > Thanks,
> > > Michal
> > > 
> > > 
> > > The following changes since commit 
> > > 97c125e6bb441a8062bdd28e82f17b1da1224416:
> > > 
> > >    Gitlab: Add results.xml to the list of artifacts as well. (2025-02-04
> > > 11:57:36 -0600)
> > > 
> > > are available in the Git repository at:
> > > 
> > >    g...@source.denx.de:u-boot/custodians/u-boot-microblaze.git
> > > tags/xilinx-for-v2025.04-rc2
> > 
> > Please note that if change your .git/config to something like:
> >     url = https://source.denx.de/u-boot/custodians/u-boot-microblaze.git
> >     pushurl = g...@source.denx.de:u-boot/custodians/u-boot-microblaze.git
> > 
> > for this remote I can then use "b4 pr" to apply these.
> 
> done. Did you switch to it?

I'm not exclusively using b4, but it's made the "acknowledge applying
patches" part of my workflow significantly easier and copy/paste of
message-id out of patchwork isn't really more work than making a bundle
to download. I still use patchwork for other parts of my flow however
such as reviewing patches for feedback.

-- 
Tom

Attachment: signature.asc
Description: PGP signature

Reply via email to