public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kent Fredric <kentfredric@gmail.com>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Re: Bug #565566: Why is it still not fixed?
Date: Thu, 25 Feb 2016 18:46:08 +1300	[thread overview]
Message-ID: <CAATnKFDAkoZEYC1=zF0hknWRzhWmMLocRBZ-pkia_RS6WQJ4cg@mail.gmail.com> (raw)
In-Reply-To: <pan$acea2$2dd6f3ac$7e97ad6f$84e32588@cox.net>

On 25 February 2016 at 18:03, Duncan <1i5t5.duncan@cox.net> wrote:
> Which I am (running from the git repo), and that ability to (as a user,
> easily) actually track all that extra data was one of my own biggest
> reasons for so looking forward to the git switch for so long, and is now
> one of the biggest reason's I'm a /huge/ supporter of the new git repo,
> in spite of the time it took and the imperfections it still has.


I'm considering bolting together some Perl that would allow you to run
a small HTTP service rooted in a git repo dir, and would then generate
given changes files on demand and then cache their results somehow.


Then you could have a "Live changes as a service" where interested
parties could simply do:

 curl http://thing.gentoo.org/changes/dev-lang/perl

and get a changelog spewed out instead of burdening the rsync server
with generating them for every sync.

That way the aggregate CPU Load would be grossly reduced because the
sync server wouldn't have to spend time generating changes for every
update/update window, and it wouldn't have to be full-tree aware.

But thinking about it makes me go "eeeh, thats a lot of effort really"

-- 
Kent

KENTNL - https://metacpan.org/author/KENTNL


  reply	other threads:[~2016-02-25  5:46 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-23 17:14 [gentoo-dev] Bug #565566: Why is it still not fixed? Patrick Lauer
2016-02-23 18:07 ` Alec Warner
2016-02-23 21:53   ` Patrick Lauer
2016-02-24  0:33     ` [gentoo-dev] " Duncan
2016-02-24  0:50       ` Kristian Fiskerstrand
2016-02-24  2:53         ` Rich Freeman
2016-02-24  4:24           ` Duncan
2016-02-24  5:49             ` Kent Fredric
2016-02-24  7:29               ` Duncan
2016-02-24 10:35                 ` Kent Fredric
2016-02-24 19:18                   ` Raymond Jennings
2016-02-24 20:16                     ` Luis Ressel
2016-02-24 21:15                       ` Daniel Campbell
2016-02-24 22:16                       ` Brian Dolbec
2016-02-25  7:12                       ` Martin Vaeth
2016-02-25 23:12                         ` Gordon Pettey
2016-02-26 11:00                           ` Martin Vaeth
2016-02-26 11:11                             ` Rich Freeman
2016-02-26 12:59                               ` Martin Vaeth
2016-02-26 13:37                                 ` Rich Freeman
2016-02-27 10:30                                   ` Martin Vaeth
2016-02-25  5:03                   ` Duncan
2016-02-25  5:46                     ` Kent Fredric [this message]
2016-02-25  8:02                       ` Consus
2016-02-25  8:59                         ` Kent Fredric
2016-02-25 10:48                           ` M. J. Everitt
2016-02-24  4:38           ` Vadim A. Misbakh-Soloviov
2016-02-24  5:36             ` Duncan
2016-02-24  2:39       ` Rich Freeman
2016-02-27 13:14       ` Luca Barbato
2016-02-27 22:35         ` Raymond Jennings
2016-02-27 22:50         ` Robin H. Johnson
2016-02-27 23:08           ` Patrick Lauer
2016-02-28  8:27             ` Martin Vaeth
2016-02-28  3:28         ` Duncan
2016-02-23 18:46 ` [gentoo-dev] " Alexis Ballier
2016-02-23 21:54   ` Patrick Lauer

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='CAATnKFDAkoZEYC1=zF0hknWRzhWmMLocRBZ-pkia_RS6WQJ4cg@mail.gmail.com' \
    --to=kentfredric@gmail.com \
    --cc=gentoo-dev@lists.gentoo.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