public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] RFC: Dropping rsync as a tree distribution method
Date: Wed, 19 Dec 2018 23:46:59 +0000	[thread overview]
Message-ID: <robbat2-20181219T234359-033909423Z@orbis-terrarum.net> (raw)
In-Reply-To: <7da3ce86-d7c5-0336-886d-c43a6144a5fb@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1149 bytes --]

On Tue, Dec 18, 2018 at 01:14:44PM -0500, Brian Evans wrote:
> I personally would be sad to see rsync go as I use the git developer
> tree as my main repository on 2 machines. This is so I can develop and
> update from the single source.  These have no news or md5-cache and it
> can be painful to generate metadata on one of them.
> I rely on scripts to pull down the rsync metadata to expedite this
> process. eg. rsync <host>/gentoo-portage/metadata/md5-cache/.
As point out elsewhere, news and md5-cache ARE available in the git sync
repos.

> Git has no easy sub-tree download equivalent that I know of.
Upstream Git does have development efforts going on towards this goal,
spearheaded by developers at Google & Microsoft, who want to work with
sub-trees in massive repos. 

Without those new enhancements, it was already possible to checkout only
a subtree (but you still had to download all of it).

-- 
Robin Hugh Johnson
Gentoo Linux: Dev, Infra Lead, Foundation Treasurer
E-Mail   : robbat2@gentoo.org
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 1113 bytes --]

      parent reply	other threads:[~2018-12-19 23:47 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-16  4:15 [gentoo-project] RFC: Dropping rsync as a tree distribution method Alec Warner
2018-12-16  4:40 ` Matt Turner
2018-12-16  5:13   ` Georgy Yakovlev
2018-12-16  5:17     ` Alec Warner
2018-12-16  6:50       ` Raymond Jennings
2018-12-16  6:52         ` Raymond Jennings
2018-12-16  7:38       ` Zac Medico
2018-12-16  7:42       ` Zac Medico
2018-12-18 17:28         ` Andrew Savchenko
2018-12-16  6:55     ` Raymond Jennings
2018-12-16 10:22     ` Toralf Förster
2018-12-17 17:26     ` Matt Turner
2018-12-17 17:43       ` Raymond Jennings
2018-12-18  3:57         ` Georgy Yakovlev
2018-12-18  4:02           ` Raymond Jennings
2018-12-18  8:06           ` Robin H. Johnson
2018-12-20  1:18           ` Kent Fredric
2018-12-16 11:34 ` Rich Freeman
2018-12-16 21:10   ` Matthew Thode
2018-12-20  1:26   ` Kent Fredric
2018-12-16 17:15 ` Toralf Förster
2018-12-16 17:38   ` M. J. Everitt
2018-12-16 18:05     ` M. J. Everitt
2018-12-16 18:36       ` Rich Freeman
2018-12-16 18:41         ` M. J. Everitt
2018-12-18  9:55 ` Andrew Savchenko
2018-12-18 11:36   ` Raymond Jennings
2018-12-18 17:14     ` Andrew Savchenko
2018-12-18 18:00       ` Alec Warner
2018-12-18 22:13         ` M. J. Everitt
2018-12-18 11:55   ` Michał Górny
2018-12-20  1:43   ` Kent Fredric
2018-12-20  2:33     ` Rich Freeman
2018-12-20 16:21       ` Kent Fredric
2018-12-18 18:14 ` Brian Evans
2018-12-18 18:37   ` Alec Warner
2018-12-18 18:38     ` Raymond Jennings
2018-12-18 20:29       ` Alec Warner
2018-12-18 18:42   ` Rich Freeman
2018-12-19 23:46   ` Robin H. Johnson [this message]

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=robbat2-20181219T234359-033909423Z@orbis-terrarum.net \
    --to=robbat2@gentoo.org \
    --cc=gentoo-project@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