Conversation
krzk

Krzysztof Kozlowski

Edited 11 months ago
I was always using git branch --edit-description && git format-patch && git send-email, but now I tried preparing and sending patchset with b4 (b4 prep && b4 send). It works great! It is trivial in use and really solves the workflow. I cannot understand why people still Cc wrong people or are unable to send one patchset properly threaded.

Edit: --edit-cover->--edit-description
3
1
15
ljs

Reply to @krzk
@krzk I always end up resorting to doing this manually with all that stuff (and occasionally making mistakes) fearing b4 would somehow screw it up but it's such an almighty pain in the arse + enough people reporting b4 working solidly that I think for my next series I should give it a go...
1
0
3
vbabka

Reply to @ljs
@ljs @krzk I've already used it for last 2 or 3 postings and it's super convenient!
1
0
3
ljs

Reply to @vbabka
@vbabka @krzk yeah seems the way to go, I'm more likely to fuck things up doing it manually tbh
1
0
1
monsieuricon

K. Ryabitsev

Reply to @ljs
@ljs @vbabka @krzk for the record, there is still a good chance things will go sideways with b4 send, but at this point it should work fairly reliably for the majority of workflows. It's only when someone tries to be more creative than we expect when things go boom.
2
0
4
ljs

Reply to @monsieuricon
@monsieuricon @krzk @vbabka luckily I am not that creative
0
0
2
abelvesa

Abel Vesa

Reply to @monsieuricon
Edited 11 months ago
@monsieuricon while at it, where did "b4 prep --cleanup" dissapear? It is still in the documentation though.

L.E. version 0.12.4 definitely doesn't have it.
1
0
0
monsieuricon

K. Ryabitsev

Reply to @abelvesa
@abelvesa it's in 0.13+ (unreleased yet)
2
0
0
abelvesa

Abel Vesa

Reply to @monsieuricon
@monsieuricon got it. Thanks.
0
0
0
abelvesa

Abel Vesa

Reply to @monsieuricon
@monsieuricon one more thing. When one wants to prepare 2 patchsets that depend on each other, b4 prep is not allowed for the second patchset, as it complains that the first branch is already a b4 prep branch (I guess it sees the b4 commit from the first patchset being there). The only workaround I found is to do b4 prep with -next first, then rebase on top of first branch and then do b4 prep for the second patchset.
0
0
0
nsa@fosstodon.org

Nuno Sá

Reply to @krzk

Finding out the web endpoint with b4 was awesome. Now I can just send patches from my personal machine since I don't have to rely on an internal (so vpn + windows) SMTP server.

0
0
0
basha@social.nayab.dev

Nayab Sayed

Reply to @krzk

@krzk Sorry, I haven't identified any reference to a git branch --edit-cover. If git branch has such an option called --edit-cover. My google-fu (and also man pages) failed me this time.

1
0
0
basha@social.nayab.dev

Nayab Sayed

Reply to @basha@social.nayab.dev

@krzk Thanks for the correction.

0
0
0
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: