-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have run into a challenge that I suspect is a limitation of current TopGit. I am hoping you could help enlighten me, as I otherwise feel that TopGit is not generally usable for my Debian packaging needs: How to manage patches against multiple source branches using TopGit? Let's take netatalk as an example. Upstream only quite infrequently release new upstream tarball releases, so I cherry-pick patches from upstream VCS. Recently a security-related bug was discovered which needed fixing not only in the current packaging development (git master branch) but also needed branching off earlier releases of the package (those included in the "stable" and "oldstable" Debian distro releases) and applying same fix for them. The actual patch needed for the various branches was obviously not identical, as upstream sources were different and my cherry-picked set of patches had evolved. It seems to me that TopGit is incapable of handling this. That it can only handle patchset against a single branch, and if the need arise for restructuring an additional patchset for e.g. a stable or oldstable branch, then quilt needs to be used manually anyway. - Jonas Debian developer - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkmtFoUACgkQn7DbMsAkQLgvrACdHfy5K0igPa6Yj/LYyhh3Llyn jvcAnRfla1QyuUrx8+L4IL9XYY2CB+Su =B1Kc -----END PGP SIGNATURE----- -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
