Re: [PATCH 2/2] transport-helper: ask the helper to set the same options for import as for fetch

2015-02-14 Thread Junio C Hamano
Mike Hommey writes: > I haven't looked exactly what cas does and if it makes sense for export. > (FWIW, I'm using push and import at the moment, so it's not a direct > issue for me ; I don't support cas anyways) The question primarily came from curiosity to gauge how much potential work remains

Re: [PATCH 2/2] transport-helper: ask the helper to set the same options for import as for fetch

2015-02-13 Thread Mike Hommey
On Fri, Feb 13, 2015 at 11:36:24AM -0800, Junio C Hamano wrote: > Mike Hommey writes: > > > A remote helper is currently only told about the 'check-connectivity', > > 'cloning', and 'update-shallow' options when it supports the 'fetch' > > command, but not when it supports 'import' instead. > >

Re: [PATCH 2/2] transport-helper: ask the helper to set the same options for import as for fetch

2015-02-13 Thread Junio C Hamano
Mike Hommey writes: > A remote helper is currently only told about the 'check-connectivity', > 'cloning', and 'update-shallow' options when it supports the 'fetch' > command, but not when it supports 'import' instead. Sounds sensible. Does the same issue exist for export vs push or do they happ

[PATCH 2/2] transport-helper: ask the helper to set the same options for import as for fetch

2015-02-12 Thread Mike Hommey
A remote helper is currently only told about the 'check-connectivity', 'cloning', and 'update-shallow' options when it supports the 'fetch' command, but not when it supports 'import' instead. This is especially important for the 'cloning' option, because it means a remote helper that only supports