[Pkg-octave-devel] Recommended workflow for creating/managing patches?

[Rafael Laboissiere]

* Sébastien Villemot <sebastien at debian.org> [2015-10-31 10:01]:

> Le mercredi 28 octobre 2015 à 14:00 +0100, Julien Bect a écrit :
>> Dear all,
>>
>> I need to create my first patch for octave-stk ;-)
>>
>> What is the recommended workflow for creating/managing patches in the 
>> Debian octave Group?
>>
>> Should I use "gbp pq" as described, e.g., here: 
>> https://honk.sigxcpu.org/piki/development/debian_packages_in_git/ 
>> http://linux.lsdev.sil.org/wiki/index.php/Packaging_using_gbp ?
>>
>> Or is there a better way?
>
> Actually we don't use git to manage the patch queue. We just use plain 
> quilt, and commit the contents of debian/patches as files in git.
>
> Given that we don't have so many patches, this appeared the simplest 
> way to us. Using gbp-pq seemed to be kind of an overkill. And, 
> moreover, when I tried it, gbp-pq would mangle the DEP3 headers of 
> patches.

I have always used the low-profile, dumb command "dpkg-source --commit" 
to generate patches.  It is not stellar, but I am happy with this 
approach.

Rafael