From: Raymond Jennings <shentino@gmail.com>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Re: Bug #565566: Why is it still not fixed?
Date: Wed, 24 Feb 2016 11:18:55 -0800 [thread overview]
Message-ID: <CAGDaZ_oO7UDTSjULEQZhEwW4T0m05iET_xJOWHtMhUD4xmJVYg@mail.gmail.com> (raw)
In-Reply-To: <CAATnKFAe_uTPn5GDZihC5eLf+9j+o613_727h4DJpyuAACkoAA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
Seems like there's a trade off in resource usage re: git vs rsync
Rsync seems to be relatively cheap, but has a fixed part of its overhead.
Probably one of the reasons that you get temp-banned from the mirrors if
you sync too often.
Git overhead appears ot be higher on the variable parts but lower on the
fixed parts, and from what I gather, the more often you sync, the lower the
overhead.
As far as changelog generation, what about causing the changelogs to be
autogenerated by the end user's computer? Divide and conquer.
[-- Attachment #2: Type: text/html, Size: 672 bytes --]
next prev parent reply other threads:[~2016-02-24 19:19 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 [this message]
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
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=CAGDaZ_oO7UDTSjULEQZhEwW4T0m05iET_xJOWHtMhUD4xmJVYg@mail.gmail.com \
--to=shentino@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