Bug#886966: Bug#886969: Problems with export-dsc and push-source on arbitrary refs

2018-06-25 Thread Sean Whitton
Hello, On Mon, Jun 25 2018, Ian Jackson wrote: >> I have not at any point looked into how split brain mode works in any >> detail. In particular, I don't know why the dgit view has to be >> stored, aside from performance reasons. > > The dgit view needs to be, err, "stored", by push, by sending

Bug#886966: Bug#886969: Problems with export-dsc and push-source on arbitrary refs

2018-06-24 Thread Ian Jackson
Sean Whitton writes ("Re: Bug#886969: Problems with export-dsc and push-source on arbitrary refs"): > On Fri, Jun 22 2018, Ian Jackson wrote: > > So I think for push-source: > > > > 886966 push-source should be usable on arbitrary refs 886625 > > push-source should be usable no matter the state

Bug#886966: Bug#886969: Problems with export-dsc and push-source on arbitrary refs

2018-06-24 Thread Sean Whitton
Hello, On Fri, Jun 22 2018, Ian Jackson wrote: > I think both export-dsc and push-source on some arbitrary ref can work > if the quilt fixup is a no-op and there is no need to make a > pseudomerge (always the case for export-dsc, but in the case of > push-source might depend on whether we're in s

Bug#886966: Bug#886969: Problems with export-dsc and push-source on arbitrary refs

2018-06-22 Thread Ian Jackson
Sean Whitton writes ("Bug#886969: Problems with export-dsc and push-source on arbitrary refs"): > My conclusion is that > - #886966 is wontfix > - #886625 can still be implemented, using playtrees > - #886969 should be the addition of an export-dsc cmd that takes no > arguments, and might commit