b4 0.4.1 available with bugfixes and minor improvements

b4 0.4.1 available with bugfixes and minor improvements

[Konstantin Ryabitsev]

Hi, all:

B4 version 0.4.1 is now available on pypi.

- ty: does a better job of preparing canned replies to short patches
- ty: is less naive about mapping local to remote branches when using them in
  templates
- ty: uses Link: and Message-Id trailers when auto-locating applied
  patches
- ty: switches -s and -d to use frienlier ranges;
  before: "-s 1 2 3 5 7 8 9", after: "-s 1-3,5,7-9"
- am: can now use the -P,--cherry-pick flag to select a subset of
  patches from a larger series

You can upgrade to the latest version from pypi using:

pip install --user --upgrade b4

Or you can use it straight from git, as before.

Special thanks in this release go to:

- Will Deacon
- Jason Gunthorpe
- Martin K. Petersen
- Lorenzo Pieralisi
- Heiko Stübner

Thanks!

-K

Re: [tools] b4 0.4.1 available with bugfixes and minor improvements

[Martin K. Petersen]

Hi Konstantin!

> - ty: is less naive about mapping local to remote branches when using
> them in templates

My ${branch} now ends up being "master" because my trees are based on
Linus' -rc1. Prior to Will's change, ${branch} emitted the local branch
name.

Maybe I could just drop tracking linus/master, I guess I do that mainly
out of habit. Not sure I've ever actually had to rebase to a later -rc.

But since b4-treename is already configurable, maybe we could have a
matching b4-branch option? Another approach would be a "these aren't the
remotes you are looking for" command line argument.

Thanks!

-- 
Martin K. Petersen	Oracle Linux Engineering

Re: [tools] b4 0.4.1 available with bugfixes and minor improvements

[Konstantin Ryabitsev]

On Tue, May 12, 2020 at 09:50:24AM -0400, Martin K. Petersen wrote:
> 
> Hi Konstantin!
> 
> > - ty: is less naive about mapping local to remote branches when using
> > them in templates
> 
> My ${branch} now ends up being "master" because my trees are based on
> Linus' -rc1. Prior to Will's change, ${branch} emitted the local branch
> name.

I literally *just* pushed out 0.4.2 that fixes that bug (and fixes the 
--auto mode). Please try that out.

> Maybe I could just drop tracking linus/master, I guess I do that mainly
> out of habit. Not sure I've ever actually had to rebase to a later -rc.
> 
> But since b4-treename is already configurable, maybe we could have a
> matching b4-branch option? Another approach would be a "these aren't the
> remotes you are looking for" command line argument.

My goal is to fit in with your workflow, not the other way around, so 
I'd rather fix the breakage -- at least for now.

-K

Re: [tools] b4 0.4.1 available with bugfixes and minor improvements

[Martin K. Petersen]

Hi Konstantin!

> I literally *just* pushed out 0.4.2 that fixes that bug (and fixes the
> --auto mode). Please try that out.

Latest still picks "master" in my case. I'm not even sure how b4 would
be able to distinguish between the two workflows (tracking a baseline
tree vs. a remote publishing branch)?

Dropping linus as a remote works. I don't really need the tracking so
that's what I'll do for now. Not a big deal.

-- 
Martin K. Petersen	Oracle Linux Engineering