On Fri, Aug 12, 2016 at 03:42:27PM +0100, Ian Jackson wrote:
> Josh Triplett writes ("Re: [ANNOUNCE] git-series: track changes to a patch
> series over time"):
> > On Fri, Aug 12, 2016 at 12:31:49PM +0100, Ian Jackson wrote:
> > > Josh Triplett writes ("Re: [ANNOUNCE] git-series: track changes to a
> > > patch series over time"):
> > > > For repositories, you can push the series branch directly if you want to
> > > > provide the history of your series, or you can push the current version
> > > > (or an older version) of the patch series if you just want to publish
> > > > that version.
> > >
> > > Neither of these is compatible with dgit, of course.
> >
> > The former seems the easiest to interoperate with: dgit could easily
> > learn to receive a series commit and turn it into a source package ready
> > for upload.
>
> I think you have fundamentally misunderstood what dgit is.
No, I understand what dgit is today. I was proposing extending it to
add additional functionality for interoperability. In any case, not
high on my priority list either.
