git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: Philip Oakley <philipoakley@iee.org>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Jeff King" <peff@peff.net>, git <git@vger.kernel.org>,
	"Derrick Stolee" <stolee@gmail.com>,
	"Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Subject: Re: Contributor Summit Topics and Logistics
Date: Thu, 31 Jan 2019 00:13:01 +0100	[thread overview]
Message-ID: <CAP8UFD1ka47UvU4CXRc5cMK=mpH0THtQkjG2-wOt2hhqLU4CsA@mail.gmail.com> (raw)
In-Reply-To: <2015d9ea-0570-b035-dcbb-ee1865381cf1@iee.org>

On Thu, Jan 31, 2019 at 12:05 AM Philip Oakley <philipoakley@iee.org> wrote:
>
> On 30/01/2019 20:57, Ævar Arnfjörð Bjarmason wrote:
> >
> > * "Big repos". We had discussions about this in years past. It's a very
> >    spawly and vague topic. Do we mean big history, big blobs, big (in
> >    size/depth/width) checkouts etc?
> >
> >    But regardless, many of us deal with this in one way or another, and
> >    it would be good to have a top-level overview of how the various
> >    solutions to this that are being integrated into git.git are doing /
> >    what people see on the horizon for scalabiltiy.

I am also very interested in that topic ;-)

> I'd also like a bit of discussion about ensuring that the partial clone
> & filtering aspects of 'big repos' (if partial is needed /used then it's
> big ...) still retain the full 'distributed' nature and capability of git.

And in this too, especially regarding my work on many promisor/partial
clone remotes (previously ODBs).

  reply	other threads:[~2019-01-30 23:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-22  7:50 Contributor Summit Topics and Logistics Jeff King
2019-01-22  8:26 ` Jeff King
2019-01-22  9:17   ` GSoC 2019 (was: Contributor Summit Topics and Logistics) Christian Couder
2019-01-31  2:02     ` SZEDER Gábor
2019-01-31  6:11       ` Christian Couder
2019-01-22 18:21   ` Contributor Summit Topics and Logistics Stefan Beller
2019-01-22 20:53     ` Jeff King
2019-01-22 18:23 ` Derrick Stolee
2019-01-24  8:57   ` Ævar Arnfjörð Bjarmason
2019-01-29 18:22     ` Derrick Stolee
2019-01-22 20:30 ` Elijah Newren
2019-01-30 20:57 ` Ævar Arnfjörð Bjarmason
2019-01-30 22:26   ` Jeff Hostetler
2019-01-30 22:51   ` Philip Oakley
2019-01-30 23:13     ` Christian Couder [this message]
2019-01-30 23:07 ` Jeff King
2019-02-02 12:33   ` Jakub Narebski
2019-02-04 19:30     ` Elijah Newren
2019-04-23  3:45     ` Jeff King

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: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAP8UFD1ka47UvU4CXRc5cMK=mpH0THtQkjG2-wOt2hhqLU4CsA@mail.gmail.com' \
    --to=christian.couder@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=philipoakley@iee.org \
    --cc=stolee@gmail.com \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).