From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org
Subject: Re: [tools] b4 0.4.1 available with bugfixes and minor improvements
Date: Tue, 12 May 2020 20:35:35 -0400 [thread overview]
Message-ID: <yq1eero1xk8.fsf@oracle.com> (raw)
In-Reply-To: <20200512135724.m5qqjogcnpivzyo4@chatter.i7.local> (Konstantin Ryabitsev's message of "Tue, 12 May 2020 09:57:24 -0400")
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
prev parent reply other threads:[~2020-05-13 0:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 19:19 b4 0.4.1 available with bugfixes and minor improvements Konstantin Ryabitsev
2020-05-12 13:50 ` [tools] " Martin K. Petersen
2020-05-12 13:57 ` Konstantin Ryabitsev
2020-05-13 0:35 ` Martin K. Petersen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yq1eero1xk8.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=konstantin@linuxfoundation.org \
--cc=tools@linux.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).