tools.linux.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: tools@linux.kernel.org
Subject: Re: b4 not finding patches
Date: Wed, 18 Mar 2020 18:18:02 -0400	[thread overview]
Message-ID: <20200318221802.25sxldeocw7dchsi@chatter.i7.local> (raw)
In-Reply-To: <20200318205914.GG4553@sirena.org.uk>

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

On Wed, Mar 18, 2020 at 08:59:14PM +0000, Mark Brown wrote:
> > I'm not sure if there is a reliably clean way of handling this 
> > situation, but I'll think about it. For this particular case, you 
> > can just pass -v1 to "b4 am" to grab the actual patches.
> 
> ...but not the tags added to the cover letter which is the main reason
> I'm doing this :/ .  I do see the issue given people sending new
> serieses in reply to existing ones though.  Perhaps some heuristic about
> lack of ambiguity (eg, if we're looking for six patches and find exactly
> six patches)?

I have code that properly handles this situation in master:

------
$ python3 b4/command.py am -o/tmp 87y2s0olg6.wl-kuninori.morimoto.gx@renesas.com -t
Looking up https://lore.kernel.org/r/87y2s0olg6.wl-kuninori.morimoto.gx@renesas.com
Grabbing thread from lore.kernel.org
Analyzing 13 messages in the thread
---
Writing /tmp/v3_20200316_kuninori_morimoto_gx_renesas_com.mbx
  [PATCH 1/6] ASoC: soc-core: Merge CPU/Codec DAIs
    Added: Reviewed-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
    Added: Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
  [PATCH 2/6] ASoC: soc-core: Merge for_each_rtd_cpu/codec_dais()
    Added: Reviewed-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
    Added: Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
  [PATCH 3/6] ASoC: soc-dapm: Merge for_each_rtd_cpu/codec_dais()
    Added: Reviewed-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
    Added: Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
  [PATCH 4/6] ASoC: soc-pcm: Merge for_each_rtd_cpu/codec_dais()
    Added: Reviewed-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
    Added: Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
  [PATCH 5/6] ASoC: soc-core: Merge CPU/Codec for soc_dai_pcm_new()
    Added: Reviewed-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
    Added: Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
  [PATCH 6/6] ASoC: soc-pcm: Merge CPU/Codec MSB at soc_pcm_apply_msb()
    Added: Reviewed-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
    Added: Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
---
Total patches: 6
---
Cover: /tmp/v3_20200316_kuninori_morimoto_gx_renesas_com.cover
 Link: https://lore.kernel.org/r/87y2s0olg6.wl-kuninori.morimoto.gx@renesas.com
 Base: not found, sorry
       git checkout -b v3_20200316_kuninori_morimoto_gx_renesas_com master
       git am /tmp/v3_20200316_kuninori_morimoto_gx_renesas_com.mbx
------

You can try that directly from the repo (if you set PYTHONPATH=.), or 
build your own package.

Alternatively, you can run:

b4 mbox 87y2s0olg6.wl-kuninori.morimoto.gx@renesas.com
(edit all subjects to add v3 to them)
b4 am 87y2s0olg6.wl-kuninori.morimoto.gx@renesas.com -m that.mbox

I'll probably release 0.3.4 tomorrow with a couple more fixes.

Best,
-K

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

  parent reply	other threads:[~2020-03-18 22:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18 20:23 b4 not finding patches Mark Brown
2020-03-18 20:38 ` Konstantin Ryabitsev
2020-03-18 20:59   ` Mark Brown
2020-03-18 21:07     ` Konstantin Ryabitsev
2020-03-18 22:18     ` Konstantin Ryabitsev [this message]
2020-03-20 20:52       ` Mark Brown

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=20200318221802.25sxldeocw7dchsi@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;
as well as URLs for NNTP newsgroup(s).