Sean Whitton writes ("Re: Bug#852090: Bug#851897: dgit: please have generated
source packages contain standard patch series"):
> On Sat, Jan 21, 2017 at 06:21:04PM +, Ian Jackson wrote:
> > I suggest adding this part...
> >
> > +to facilitate
> &
Ian Jackson wrote on Sat, Jan 21, 2017 at 20:42:40 +:
> This is a good direction. I now have:
>
>The Debian packaging of foo is maintained in git,
>using the merging workflow described in dgit-maint-merge(7).
> | There isn't a patch queue that can be represented as a quilt series.
>
Hello again,
We've two separate bugs, but I'll just address my feedback to both of
them, to minimise the number of e-mails you two receive. I'm sorry for
not having made best use of the BTS 'clone' command earlier today.
changes to manpage introduction (#852090)
On Sat, Jan 21, 2017
Daniel Shahaf writes ("Re: Bug#851897: dgit: please have generated source
packages contain standard patch series"):
> The language "automatically generated representation" raises the
> "inferior representation" v. "best possible representation in the
&g
Ian Jackson wrote on Sat, Jan 21, 2017 at 18:21:04 +:
> How about this. Comments interleaved:
>
> @@ -23,7 +23,9 @@ the usefulness of the raw Debian source package. The
> Debian archive
>is thought of as an output format.
>
>For example, we don't spend time curating a series of
How about this. Comments interleaved:
@@ -23,7 +23,9 @@ the usefulness of the raw Debian source package. The
Debian archive
is thought of as an output format.
For example, we don't spend time curating a series of quilt patches.
-However, the information such a series would contain
Sean Whitton wrote on Fri, Jan 20, 2017 at 14:16:28 -0700:
> On Fri, Jan 20, 2017 at 03:52:09PM +, Daniel Shahaf wrote:
> > Ian Jackson wrote on Fri, Jan 20, 2017 at 00:21:56 +:
> > > Let me quote yur preferred wording from your patch. (I find it easier
> > > to deal with this inline as
Sean Whitton wrote on Fri, Jan 20, 2017 at 14:32:16 -0700:
> On Fri, Jan 20, 2017 at 12:21:56AM +, Ian Jackson wrote:
> >This workflow is less suitable for some packages. When the Debian
> >delta contains multiple pieces which interact, or which you aren't
> >going to be able to
Hello Ian, Daniel,
On Fri, Jan 20, 2017 at 12:21:56AM +, Ian Jackson wrote:
> Lack of a coherent patch stack is a problem if the individual patches
> are hard to extract from the history, which occurs when the patches
> need adjustment or conflict resolution to conform to new upstreams, or
>
[replying separately as this is tangential]
Hello Daniel,
On Fri, Jan 20, 2017 at 03:52:09PM +, Daniel Shahaf wrote:
> Ian Jackson wrote on Fri, Jan 20, 2017 at 00:21:56 +:
> > Let me quote yur preferred wording from your patch. (I find it easier
> > to deal with this inline as prose
Ian Jackson wrote on Fri, Jan 20, 2017 at 00:21:56 +:
> Let me quote yur preferred wording from your patch. (I find it easier
> to deal with this inline as prose than as an attachment. And I'd like
> Daniel's opinion, as someone who has to deal with "not their own"
> packages, before
Control: tags -1 patch
Hi again Sean. Thanks for the quick reply.
> Instead, I'd like to add text to say something about the kinds of
> packages for which the workflow is unsuitable. I'd already been
> thinking about submitting a patch to do that since the recent discussion
> on -devel, and I
control: tag -1 +patch
Dear Daniel, Ian,
Thank you for this feedback.
On Thu, Jan 19, 2017 at 05:09:26PM +, Daniel Shahaf wrote:
> Some source packages generated by dgit have a single debian patch, with
> instructions in debian/source/patch-header to use dgit to obtain the
> patch series.
Control: severity -1 normal
Control: retitle -1 dgit-maint-merge(7): clarify patch series non-goal
Daniel Shahaf writes ("Bug#851897: dgit: please have generated source packages
contain standard patch series"):
> Some source packages generated by dgit have a single
Package: dgit
Version: 3.5
Severity: wishlist
Tags: upstream
Dear Maintainer,
Some source packages generated by dgit have a single debian patch, with
instructions in debian/source/patch-header to use dgit to obtain the
patch series. That's advised by dgit-maint-merge(7).
Please consider having
15 matches
Mail list logo
