From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: git@vger.kernel.org, meta@public-inbox.org
Subject: Re: "IMAP IDLE"-like long-polling "git fetch"
Date: Sat, 29 Dec 2018 06:13:52 +0000 [thread overview]
Message-ID: <20181229061352.GA5935@dcvr> (raw)
In-Reply-To: <20181229043858.GA28509@pure.paranoia.local>
Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> On Sat, Dec 29, 2018 at 03:56:21AM +0000, Eric Wong wrote:
> > Hey all, I just added this to the TODO file for public-inbox[1] but
> > obviously it's intended for git.git (meta@public-inbox cc-ed):
> >
> > > +* Contribute something like IMAP IDLE for "git fetch".
> > > + Inboxes (and any git repos) can be kept up-to-date without
> > > + relying on polling.
> >
> > I would've thought somebody had done this by now, but I guess
> > it's dependent on a bunch of things (TLS layer nowadays, maybe
> > HTTP/2), so git-daemon support alone wouldn't cut it...
>
> Polling is not all bad, especially for large repository collections. I'm
> not sure you want to "idle" individual repositories when there's
> thousands of them. We ended up writing grokmirror for replicating
> repo collections using manifest files.
I wasn't intending it for giant sites like korg, but for
individual hackers on their workstations tracking a handful of
projects they follow.
The cost for a hackers' machine would be the same as the current
situation where developers idle on IRC channels for the projects
they're involved in.
> > Anyways, until this is implemented, feel free to continue
> > hammering a way on https://public-inbox.org/git/ with frequent
> > "git fetch". I write C10K servers in my sleep -_-
>
> The archive is also mirrored at
> https://git.kernel.org/pub/scm/public-inbox/vger.kernel.org/git.git, and
> also on kernel.googlesource.com.
Now, I'm wondering if you can make a v2 public-inbox mirror of
git@vger and run it on lore. Converting public-inbox.org/git to
v2 would break things for everybody fetching, right now :<
next prev parent reply other threads:[~2018-12-29 6:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-29 3:43 [PATCH] TODO: add note for "IMAP IDLE"-like long-polling "git fetch" Eric Wong
2018-12-29 3:56 ` Eric Wong
2018-12-29 4:38 ` Konstantin Ryabitsev
2018-12-29 6:13 ` Eric Wong [this message]
2019-01-09 22:27 ` Stefan Beller
2019-01-09 22:49 ` Konstantin Ryabitsev
2019-05-02 8:50 ` Eric Wong
2019-05-02 9:21 ` Ævar Arnfjörð Bjarmason
2019-05-02 9:42 ` 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=20181229061352.GA5935@dcvr \
--to=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=konstantin@linuxfoundation.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.
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).