Control: tags -1 pending
Sean wrote:
> I agree with the general thought. Are you saying you wouldn't
> accept a patch adding the smash-all strategy?
I've improved the error messages and the docs in this area.
I don't think I want to add that new --quilt strategy that you
suggest. If that's
Hello,
On Mon, Aug 01, 2016 at 10:42:53AM +0100, Ian Jackson wrote:
> Sean Whitton writes ("Bug#833025: dgit: quiltify smash strategy shouldn't
> fail when current patch queue fails to apply"):
> > I am the maintainer, but I think that there are use cases for a d
Sean Whitton writes ("Bug#833025: dgit: quiltify smash strategy shouldn't fail
when current patch queue fails to apply"):
> I am the maintainer, but I think that there are use cases for a dgit
> quilt strategy that is essentially a one-shot single-debian-patch.
>
> Su
Hello,
On Sun, Jul 31, 2016 at 11:50:40AM +0100, Ian Jackson wrote:
> My concepton of --quilt=smash was to allow an NMUer to generate a
> single additional patch out of what in git is a merge (or other
> excitement).
That makes sense.
> > For example, today I merged a new upstream version to a
Sean Whitton writes ("Bug#833025: dgit: quiltify smash strategy shouldn't fail
when current patch queue fails to apply"):
> The smash strategy should not fail when the current contents of
> debian/patches/ does not apply cleanly to the upstream source.
Indeed.
> Intui
Package: dgit
Version: 1.4
Severity: normal
The smash strategy should not fail when the current contents of
debian/patches/ does not apply cleanly to the upstream source.
Intuitively, one meaning of the smash strategy is "I know that no sane
linearisation can be automatically generated from the
6 matches
Mail list logo
