Re: Keeping a non-1:1 mirror in sync and keeping private branches

2017-07-16 Thread Jeff King
On Sun, Jul 16, 2017 at 03:42:09PM +0200, Jan Danielsson wrote: > > 1. Drop the pruning (in which case deleted branches from the sync may > > accumulate, but depending on the patterns that may or may not be a > > problem). > >I don't think that's a problem. Or rather, I'd be

Re: Keeping a non-1:1 mirror in sync and keeping private branches

2017-07-16 Thread Jan Danielsson
On 07/16/17 12:10, Jeff King wrote: >>This seems to accomplish everything I want except that the the "git >> push" deletes any branches I have created on my self-hosted >> repository. > > A mirrored push is basically: > > - push all refs, i.e., a "+refs/*:refs/*" refspec > > - enable

Re: Keeping a non-1:1 mirror in sync and keeping private branches

2017-07-16 Thread Jeff King
On Sun, Jul 16, 2017 at 02:59:23AM +0200, Jan Danielsson wrote: >This seems to accomplish everything I want except that the the "git > push" deletes any branches I have created on my self-hosted > repository. A mirrored push is basically: - push all refs, i.e., a "+refs/*:refs/*" refspec

Keeping a non-1:1 mirror in sync and keeping private branches

2017-07-15 Thread Jan Danielsson
Hello, Let's say there'a s hosting service hosting a repository which I want to self-host. I don't just want to do a mirror, but I want to keep it in sync (using a cronjob). In addition, I want to have private branches on the self-hosted repository. (In this particular case, the "hosting