user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: meta@public-inbox.org
Subject: lei import on epochs [was: make menuconfig interface for lei / grok-pull]
Date: Thu, 16 Sep 2021 21:09:02 +0000	[thread overview]
Message-ID: <20210916210902.GA28336@dcvr> (raw)
In-Reply-To: <YUJm8F5E174ZSGgC@bombadil.infradead.org>

Luis Chamberlain <mcgrof@kernel.org> wrote:
> # The next two don't work
> lei import import https://lore.kernel.org/linux-fsdevel/git/0.git

Btw, extra "import" aside; I never intended to support the above
case.  However, your post got me thinking we could and probably
should... :>

(epochs are git storage with a loose limit of ~1G packed data,
 "slices" are public-inbox-imapd folders capped at 50K to
 accomodate limitations of existing clients/filesystems)

  parent reply	other threads:[~2021-09-16 21:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-15 21:34 make menuconfig interface for lei / grok-pull Luis Chamberlain
2021-09-15 21:44 ` Eric Wong
2021-09-15 21:57   ` Luis Chamberlain
2021-09-15 23:12     ` Eric Wong
2021-09-15 22:36   ` Kyle Meyer
2021-09-15 23:31     ` Eric Wong
2021-09-16  2:59   ` Eric Wong
2021-09-15 23:06 ` Eric Wong
2021-09-16 17:43   ` Konstantin Ryabitsev
2021-09-16 20:04     ` IMAP vs NNTP [was: make menuconfig interface for lei / grok-pull] Eric Wong
2021-09-19 21:21   ` make menuconfig interface for lei / grok-pull Eric Wong
2021-09-16 17:38 ` Konstantin Ryabitsev
2021-09-16 23:54   ` Luis Chamberlain
2021-09-16 21:09 ` Eric Wong [this message]
2021-09-16 23:53   ` lei import on epochs [was: make menuconfig interface for lei / grok-pull] Luis Chamberlain
2021-09-17  0:22     ` Eric Wong
2021-09-17  0:48       ` Luis Chamberlain

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

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210916210902.GA28336@dcvr \
    --to=e@80x24.org \
    --cc=mcgrof@kernel.org \
    --cc=meta@public-inbox.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.
Code repositories for project(s) associated with this inbox:

	https://80x24.org/public-inbox.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).