Re: [ANNOUNCE] Git Merge Contributor Summit topic planning

2017-02-01 Thread Junio C Hamano
Jeff King writes: > For instance, if the server knew that XYZ meant > > - send bytes m through n of packfile p, then... > > - send the object at position i of packfile p, as a delta against the > object at position j of packfile q > > - ...and so on > > Then you could

Re: [ANNOUNCE] Git Merge Contributor Summit topic planning

2017-02-01 Thread Jeff King
On Wed, Feb 01, 2017 at 10:06:15AM -0800, Junio C Hamano wrote: > > If you _can_ do that latter part, and you take "I only care about > > resumability" to the simplest extreme, you'd probably end up with a > > protocol more like: > > > > Client: I need a packfile with this want/have > >

Re: [ANNOUNCE] Git Merge Contributor Summit topic planning

2017-02-01 Thread Stefan Beller
On Mon, Jan 30, 2017 at 4:48 PM, Jeff King wrote: > The Contributor Summit is only a few days away; I'd like to work out a > few bits of logistics ahead of time. > > We're up to 26 attendees. The room layout will probably be three big > round-tables, with a central projector. We

Re: [ANNOUNCE] Git Merge Contributor Summit topic planning

2017-02-01 Thread Christian Couder
On Tue, Jan 31, 2017 at 1:59 AM, Jeff King wrote: > On Tue, Jan 31, 2017 at 01:48:05AM +0100, Jeff King wrote: > >> The list of topics is totally open. If you're coming and have something >> you'd like to present or discuss, then propose it here. If you're _not_ >> coming, you may

Re: [ANNOUNCE] Git Merge Contributor Summit topic planning

2017-02-01 Thread Junio C Hamano
Jeff King writes: > If you _can_ do that latter part, and you take "I only care about > resumability" to the simplest extreme, you'd probably end up with a > protocol more like: > > Client: I need a packfile with this want/have > Server: OK, here it is; its opaque id is XYZ. >

Re: [ANNOUNCE] Git Merge Contributor Summit topic planning

2017-02-01 Thread Jeff King
On Wed, Feb 01, 2017 at 10:32:12AM +0100, Erik van Zijst wrote: > Clients performing a full clone get redirected to a CDN where they seed > their new local repo from a pre-built bundle file, and then pull/fetch > any remaining changes. Mercurial has had native, built-in support for > this for a

Re: [ANNOUNCE] Git Merge Contributor Summit topic planning

2017-02-01 Thread Erik van Zijst
On Tue, Jan 31, 2017 at 01:48:05AM +0100, Jeff King wrote: > The list of topics is totally open. If you're coming and have something > you'd like to present or discuss, then propose it here. If you're _not_ > coming, you may still chime in with input on topics, but please don't > suggest a topic

Re: [ANNOUNCE] Git Merge Contributor Summit topic planning

2017-01-30 Thread Jeff King
On Tue, Jan 31, 2017 at 01:48:05AM +0100, Jeff King wrote: > The list of topics is totally open. If you're coming and have something > you'd like to present or discuss, then propose it here. If you're _not_ > coming, you may still chime in with input on topics, but please don't > suggest a topic

[ANNOUNCE] Git Merge Contributor Summit topic planning

2017-01-30 Thread Jeff King
The Contributor Summit is only a few days away; I'd like to work out a few bits of logistics ahead of time. We're up to 26 attendees. The room layout will probably be three big round-tables, with a central projector. We should be able to have everybody pay attention to a single speaker, or break