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

[Sébastien Villemot]

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.

-- 
 .''`.    Sébastien Villemot
: :' :    Debian Developer
`. `'     http://sebastien.villemot.name
  `-      GPG Key: 4096R/381A7594



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-octave-devel/attachments/20151031/ebdfab2f/attachment.sig>