Re: general question about quilt patch handling

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 > If the changelog says 'removing/updating foo support because blah > no longer available' then there is no need to say 'and I refreshed > all my patches' too - that's just as anspect of makig it work > nicely. Perfect, thanks so I won't mention

Re: general question about quilt patch handling

+++ Werner Detter [2015-12-01 13:01 +0100]: > Hi, > > > Have you got any reason not to simply refresh your patches? > > Something like: quilt pop -a; while quilt push; do quilt refresh; done > > well, there is no reason. I'm asking because this is the first time > I have this topic. Sure,

Re: general question about quilt patch handling

Werner Detter writes: >> For example, if 3.patch has not been forwarded upstream yet, then I >> would definitely modify it (instead of creating a new patch). > > I've modified 3.patch - in the course of the modification one line has > been deleted (perl "use"

Re: general question about quilt patch handling

Hi, > Have you got any reason not to simply refresh your patches? > Something like: quilt pop -a; while quilt push; do quilt refresh; done well, there is no reason. I'm asking because this is the first time I have this topic. Sure, refreshing all patches would be probably the best - but do I

Re: general question about quilt patch handling

Werner Detter writes: >> Have you got any reason not to simply refresh your patches? >> Something like: quilt pop -a; while quilt push; do quilt refresh; done > > well, there is no reason. I'm asking because this is the first time > I have this topic. Sure, refreshing

Re: general question about quilt patch handling

Hi, > For example, if 3.patch has not been forwarded upstream yet, then I > would definitely modify it (instead of creating a new patch). I've modified 3.patch - in the course of the modification one line has been deleted (perl "use" statement) as it's not needed anymore. Therefore some

Re: general question about quilt patch handling

> For example, if 3.patch has not been forwarded upstream yet, then I > would definitely modify it (instead of creating a new patch). > > That way upstream would receive a single patch about the issue, not a > patch and a patch for the patch. thanks for your reply. Upstream is not active

general question about quilt patch handling

Hi everbody, short question by example: quilt series contains several patches, e.g. 1.patch 2.patch 3.patch 4.patch let's assume 3.patch which worked for some time but will be no longer functional because the 3.patch uses a function which will not available in future versions of dependency

Re: general question about quilt patch handling

On Sat, Nov 28, 2015 at 03:00:47PM +0100, Werner Detter wrote: > short question by example: quilt series contains several patches, e.g. > > 1.patch > 2.patch > 3.patch > 4.patch > > let's assume 3.patch which worked for some time but will be no longer > functional > because the 3.patch uses a