From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: tools@linux.kernel.org
Subject: Re: b4 ty doesn't respect -b for prs
Date: Thu, 23 Apr 2020 11:07:43 -0400 [thread overview]
Message-ID: <20200423150743.xtjmpgukvidqcghw@chatter.i7.local> (raw)
In-Reply-To: <20200423101733.GA4808@sirena.org.uk>
On Thu, Apr 23, 2020 at 11:17:33AM +0100, Mark Brown wrote:
> > > (asoc-5.7 is for-5.7 in my sound tree, the merge commit is now
> > > published.)
>
> > I see that your message says "undefined" here:
> > https://lore.kernel.org/alsa-devel/158756395814.23495.171205742201395813.b4-ty@kernel.org/
>
> > I'll see if I can find something nicer for it to say instead.
>
> I'm not sure there's something fundamentally better - it's basically
> "local tree" and not all of my local branches are tagged as tracking
> branches in git. Should've proofread properly before I sent it out.
Well, even if it says "local tree" as the fallback default for
${treename}, that will be more informative than "undefined". That's what
I'll probably set it to.
-K
prev parent reply other threads:[~2020-04-23 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 14:06 b4 ty doesn't respect -b for prs Mark Brown
2020-04-22 22:43 ` Konstantin Ryabitsev
2020-04-23 10:17 ` Mark Brown
2020-04-23 15:07 ` Konstantin Ryabitsev [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=20200423150743.xtjmpgukvidqcghw@chatter.i7.local \
--to=konstantin@linuxfoundation.org \
--cc=broonie@kernel.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