Removed the 'patch' tag as there's no patch fixing the actual bug, just a patch showing how the bug happens.
First we'd need a fixed version of splitpatch in a development Ubuntu version. http://launchpad.net/ubuntu/+source/splitpatch shows that there's a newer git snapshot in newer Ubuntus, although even that does not include the 2014 changes.
When/if the splitpatch would be fixed in a development Ubuntu version and a patch fixing this single issue found, the next step would be to update this bug according to https://wiki.ubuntu.com/StableReleaseUpdates to prepare backporting the fix to 14.04.
Removed the 'patch' tag as there's no patch fixing the actual bug, just a patch showing how the bug happens.
First we'd need a fixed version of splitpatch in a development Ubuntu version. http:// launchpad. net/ubuntu/ +source/ splitpatch shows that there's a newer git snapshot in newer Ubuntus, although even that does not include the 2014 changes.
When/if the splitpatch would be fixed in a development Ubuntu version and a patch fixing this single issue found, the next step would be to update this bug according to https:/ /wiki.ubuntu. com/StableRelea seUpdates to prepare backporting the fix to 14.04.
But first, it would be worth testing whether the 0.0+20131223+ gitb13d810- 1 version already fixes the issue, it's 6 months newer than the version in 14.04. The https:/ /launchpad. net/ubuntu/ +archive/ primary/ +files/ splitpatch_ 0.0%2B20131223% 2Bgitb13d810- 1_all.deb package probably works just fine on 14.04 too since there are no dependency changes.