Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: "Mark Brown" <broonie@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org
Subject: Re: b4 ty doesn't respect -b for prs
Date: Thu, 23 Apr 2020 11:17:33 +0100	[thread overview]
Message-ID: <20200423101733.GA4808@sirena.org.uk> (raw)
In-Reply-To: <20200422224345.jx7f6w7h4aisae6v@chatter.i7.local>

[-- Attachment #1: Type: text/plain, Size: 840 bytes --]

On Wed, Apr 22, 2020 at 06:43:45PM -0400, Konstantin Ryabitsev wrote:
> On Wed, Apr 22, 2020 at 03:06:37PM +0100, Mark Brown wrote:

> >   Generating 1 thank-you letters
> >   Writing: ./thierry_reding_gmail_com_git_pull_asoc_tegra_fixes_for_v5_7_rc3.thanks

> Good find -- there is a fix for this in master.

Thanks.

> > (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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 499 bytes --]

  reply	other threads:[~2020-04-23 10:17 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 [this message]
2020-04-23 15:07     ` Konstantin Ryabitsev

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=20200423101733.GA4808@sirena.org.uk \
    --to=broonie@kernel.org \
    --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