All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: tools@linux.kernel.org
Subject: Re: grokmirror and pi-piper for all emails on a list
Date: Fri, 28 May 2021 15:53:20 -0400	[thread overview]
Message-ID: <20210528195320.c2vbhfg3zj365ebw@nitro.local> (raw)
In-Reply-To: <CAB=NE6We=Vr8hDOBVmfiZxZyDqJXXfA9yz5t13aqMwdrp7pBZA@mail.gmail.com>

On Fri, May 28, 2021 at 12:46:03PM -0700, Luis Chamberlain wrote:
> > Note, that if you
> > configured pi-piper to reshallow the repository, you will need to unshallow it
> > first (see the article you linked above).
> 
> OK so do you mean that if I'm starting from scratch I should use the
> shallow setting or make sure to not use it?

If you're starting from scratch, make sure you don't use it, or set it after
you're done passing everything through pi-piper.

> > Also of note is that the upcoming "lei" tool from public-inbox is going to be
> > a much more robust approach to doing what pi-piper does. I really wrote it
> > mostly so we could feed lore lists into patchwork. :)
> 
> Whoa, ok so, before I go on raving about this, I should wait instead
> and rave about lei later?

You can use lei right now if you like -- I believe it is fairly stable.
I believe the docs are still pretty thin, though, and may require newer sever
deployments than what is currently running on lore.kernel.org.

I'm supposed to be giving a talk on lei, lore and b4 at the plumbers
conference this September, so I'm hoping that everything will be in a better
position to "just work out of the box" closer to that time.

-K

  reply	other threads:[~2021-05-28 19:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-28 19:14 grokmirror and pi-piper for all emails on a list Luis Chamberlain
2021-05-28 19:38 ` Konstantin Ryabitsev
2021-05-28 19:46   ` Luis Chamberlain
2021-05-28 19:53     ` Konstantin Ryabitsev [this message]
2021-05-28 20:34       ` Luis Chamberlain
2021-05-28 20:46         ` Luis Chamberlain
2021-05-28 22:42           ` Luis Chamberlain
2021-05-28 21:09         ` 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=20210528195320.c2vbhfg3zj365ebw@nitro.local \
    --to=konstantin@linuxfoundation.org \
    --cc=mcgrof@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.