The real issue is that udd-patchsys and patches-to-packages both take fairly different approaches. We need to decide which we recommend.
udd-patchsys suggest hacking directly in the branch that exporting a patch with `bzr diff -p "a/:b/"` Then importing that back with `quilt import` and reverting the changes made directly to the files.
patches-to-packages uses the normal quilt workflow of `quilt new patch.diff`, `quilt add src-file`, hack, `quilt refresh`
My thought is that patches-to-packages is closer to what we want. While the way udd-patchsys recommends is pretty nifty, it seems to me that the patches-to-packages pure quilt workflow is more widely used. Anyone else have any thoughts?
udd-patchsys also has some info on edit-patch which we should probably retain (and maybe even expand a bit on using some of the old wiki content).
Sorry for not getting to this earlier.
The real issue is that udd-patchsys and patches-to-packages both take fairly different approaches. We need to decide which we recommend.
udd-patchsys suggest hacking directly in the branch that exporting a patch with `bzr diff -p "a/:b/"` Then importing that back with `quilt import` and reverting the changes made directly to the files.
patches-to-packages uses the normal quilt workflow of `quilt new patch.diff`, `quilt add src-file`, hack, `quilt refresh`
My thought is that patches-to-packages is closer to what we want. While the way udd-patchsys recommends is pretty nifty, it seems to me that the patches-to-packages pure quilt workflow is more widely used. Anyone else have any thoughts?
udd-patchsys also has some info on edit-patch which we should probably retain (and maybe even expand a bit on using some of the old wiki content).