tools.linux.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: tools@linux.kernel.org
Subject: Re: backfilling threads with b4 (was: Re: [MAINTAINER SUMMIT] Rethinking the acceptance policy for "trivial" patches)
Date: Thu, 22 Apr 2021 21:51:59 +0300	[thread overview]
Message-ID: <YIHFzwXCDjWTLdA9@unreal> (raw)
In-Reply-To: <20210422180540.hj6xs75sqlmnegs6@nitro.local>

On Thu, Apr 22, 2021 at 02:05:40PM -0400, Konstantin Ryabitsev wrote:
> On Thu, Apr 22, 2021 at 08:56:45PM +0300, Leon Romanovsky wrote:
> > >     macro index 4 "<pipe-message>~/work/git/korg/b4/b4.sh mbox -f -o ~/Mail<return>"
> > > 
> > > You'll need to adjust it to point at where your maildir lives, of course, but
> > > that's the general idea. With it in place, you can hit "4" in the index view
> > > to get the rest of the thread (without duplicating the messages you already
> > > have).
> > 
> > Konstantin,
> > 
> > I tried the above and here the obstacles which I encounter.
> 
> This is probably better suited for tools@linux.kernel.org (cc'ing
> accordingly).
> 
> > 1. My emails are stored in Maildir. The mb2md script half-worked but ok
> > for the test.
> > 2. b4 didn't work if I tried to use lore link from the middle of discussion,
> > which is very common pattern to me.
> > 3. b4 didn't grab the discussions, so I got the patches, but didn't get and
> > won't get any interesting to me responses.
> 
> Are you sure you copied the command correctly? 
> 
> 1. It should automatically recognize when it's pointed at a maildir, so no
>    mb2md should be necessary. Are you sure you changed "-o ~/Mail" to be
>    pointing at your maildir?

I didn't want experiment on my main maildir folder so pointed to /tmp,
and didn't know that b4 recognizes format.

> 2. It's supposed to grab the message-id from the piped message, so you
>    shouldn't need to pass any lore links.

I didn't pass any links, just used as a "feed" one of the replies to the
series which I don't have.

> 3. Are you sure you're using "b4 mbox" not "b4 am"? The mbox command just
>    returns the entire thread.

Yes, I used mbox, but will retest it tomorrow, maybe I did something wrong.

> 
> Please feel free to drop ksummit and others on your reply.
> 
> -K

  reply	other threads:[~2021-04-22 18:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <afc5664dc2b60f912dd97abfa818b3f7c4237b92.camel@HansenPartnership.com>
     [not found] ` <YID5xhy2vv45fnOv@unreal>
     [not found]   ` <20210422112001.22c64fe9@coco.lan>
     [not found]     ` <20210422125357.uuxprp6rqxewcdsr@nitro.local>
     [not found]       ` <YIG43TuqmxU24evq@unreal>
2021-04-22 18:05         ` backfilling threads with b4 (was: Re: [MAINTAINER SUMMIT] Rethinking the acceptance policy for "trivial" patches) Konstantin Ryabitsev
2021-04-22 18:51           ` Leon Romanovsky [this message]
2021-04-25 10:58           ` Leon Romanovsky
     [not found]     ` <YIFfXTVMDmHwVmSR@unreal>
     [not found]       ` <20210422092916.556e5e50@gandalf.local.home>
     [not found]         ` <CAL_JsqKS-=shqkLhzKeLHqNPhosGJw5X-fOi+dy1rT3Q_LfBZg@mail.gmail.com>
2021-04-23  6:04           ` [MAINTAINER SUMMIT] Rethinking the acceptance policy for "trivial" patches Mauro Carvalho Chehab
2021-04-23  6:46             ` Joe Perches
2021-04-23  7:13               ` Mauro Carvalho Chehab
2021-04-23  7:20                 ` [PATCH RFC] scripts: add a script for sending patches Mauro Carvalho Chehab
2021-04-23 14:52                 ` Better tools for sending patches (was: Re: [MAINTAINER SUMMIT] Rethinking the acceptance policy for "trivial" patches) Doug Anderson
2021-04-23 16:03                   ` Mark Brown
2021-04-23 17:12                     ` Leon Romanovsky
2021-04-26 23:50                       ` Simon Glass

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=YIHFzwXCDjWTLdA9@unreal \
    --to=leon@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).