From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project <gentoo-project@lists.gentoo.org>
Subject: Re: [gentoo-project] RFC: Dropping rsync as a tree distribution method
Date: Wed, 19 Dec 2018 21:33:29 -0500 [thread overview]
Message-ID: <CAGfcS_=rLyRn=ONOpBQQvhMVM56k8E_5df1G05EQmkKOi8fXYA@mail.gmail.com> (raw)
In-Reply-To: <20181220144307.58a98bc1@katipo2.lan>
On Wed, Dec 19, 2018 at 8:43 PM Kent Fredric <kentnl@gentoo.org> wrote:
>
> I suspect a published list of SHA1's broken down by time might also
> help here in conjunction with passing required ones as "refspec" values
> to fetch, which would also approximate the bundle strategy, albeit
> using substantially less server-side storage space.
I'm not sure how necessary this is, but another way to do this is to
just use tags, perhaps date-based (eg year-month). Perhaps this could
be combined with some level of QA as well to ensure the tree is clean
at the time it was tagged. From the command line this would be
simpler than copy/pasting hashes from some webpage, but it obviously
clutters the repo. Granted, it isn't much clutter if you only do it
monthly.
Git fetch does not seem to support any kind of relative refspec. You
need a hash/branch/tag/ref. Git ls-remote just lists refs and not
history.
If super-unreliable connections are the concern it probably would be
cleaner to just use the previous suggestion of providing bundles with
resume support. They can be downloaded and then pulled/fetched from.
Do we really have that much of a need for this?
--
Rich
next prev parent reply other threads:[~2018-12-20 2:33 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 [this message]
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
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='CAGfcS_=rLyRn=ONOpBQQvhMVM56k8E_5df1G05EQmkKOi8fXYA@mail.gmail.com' \
--to=rich0@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