user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Eric Wong <e@80x24.org>, meta@public-inbox.org
Subject: Re: RFC: monthly epochs for v2
Date: Tue, 29 Oct 2019 11:55:20 -0400	[thread overview]
Message-ID: <20191029155520.w5nnxtt4b6v6dgun@pure.paranoia.local> (raw)
In-Reply-To: <87mudjlhkg.fsf@x220.int.ebiederm.org>

On Tue, Oct 29, 2019 at 10:03:43AM -0500, Eric W. Biederman wrote:
> So not monthly epochs.  But it would be very handing to have a
> public-inbox command command that refreshes git mirrors.  It would
> be even more awesome if there was something like the IMAP IDLE command
> in http that would let a process block until an update happened and
> then fetch the updated data.
> 
> ssoma had some of that.
> 
> I have a very rough script that works, but I periodically need to find
> the new epochs start a new mirror by hand.  So it would be nice if we
> could get a more polished tool that I could just tell it mirror this
> mailing list.  Or mirror all of the mailling lists on lore.

You can use manifest files to recognize when a new epoch is available
(and if there are new updates). E.g.:

http://lore.kernel.org/lkml/manifest.js.gz

It's written to be consumed by grokmirror, but it can be adapted to be
used by any other tool. The format is straightforward and simple to
understand.

-K

  reply	other threads:[~2019-10-29 15:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24 19:53 RFC: monthly epochs for v2 Konstantin Ryabitsev
2019-10-24 20:35 ` Eric Wong
2019-10-24 21:21   ` Konstantin Ryabitsev
2019-10-24 22:34     ` Eric Wong
2019-10-25 12:22       ` Eric Wong
2019-10-25 20:56         ` Konstantin Ryabitsev
2019-10-25 22:57           ` Eric Wong
2019-10-29 15:03             ` Eric W. Biederman
2019-10-29 15:55               ` Konstantin Ryabitsev [this message]
2019-10-29 22:46                 ` Eric Wong

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=20191029155520.w5nnxtt4b6v6dgun@pure.paranoia.local \
    --to=konstantin@linuxfoundation.org \
    --cc=e@80x24.org \
    --cc=ebiederm@xmission.com \
    --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 public 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).