Hah - I'm now so used to b4 that I am really struggling to send just a single patch. #B4Addict
@monsieuricon @pdp7 @vbabka I didn't ping because I assumed it was an arch packaging thing tbh.
God damn it I just rubber duckied myself and realised the mistake I made...
It's working now :P
Needed to b4 prep -n [branch name] before any b4 send...
LOOK AWAY SIR
@ljs @monsieuricon @pdp7 @vbabka you know the saying, it's always PEBKAC. Then it's DNS
@mathieu @monsieuricon @pdp7 @vbabka haha yeah.
The python error on b4 send without proper prep set up is a bit brutal though, it's a key error on a 'series' var.
An output like:
'you idiot, you forgot to prep!'
Would be good.
Also:
$ b4 prep
Seems to just do nothing (might be wrong though), be good to sort of warn 'yo bro, what you doing?'
Wasn't clear to me you needed to specify -n blahdyblah
I might not have excuses not to use this now
@mairacanal @vbabka @pdp7 yeah I'm possibly ready for this. Maybe.
Might try a trivial patch with it today.
Like deleting bits of DRM or something
@monsieuricon @mathieu @pdp7 @vbabka thanks!
Allow my hollow-brained apeness to guide the way
@ljs @monsieuricon @pdp7 @vbabka feel free to ping me in the future, I happen to package this thing for Arch ;)
@gromit @monsieuricon @pdp7 @vbabka it turns out it was pebkac (i.e. my fault) haha, cheers though!
@monsieuricon @mathieu @pdp7 @vbabka another issue is it seems that the generated patch puts the S-o-b line below an inserted --- line which Andrew complained about - https://lore.kernel.org/linux-mm/20250528155218.a8b755912d1eed25148c59b4@linux-foundation.org/
I did think that was a bit odd when I saw it, maybe I'm doing something wrong here? Or is there a config option to stop it doing that?
Thanks!