Hy Luke, You answered me in Ubuntu Accessibility list I need using the diff -u argument when need generating a diff file, because unified diff files is easyest readable. I need generating again the patches, or now the attached patches are will be good when you uploading new upstream release? I now using diff -p argument with patch generation, for example: diff -p src/orca/scripts/default.py.old src/orca/scripts/default.py >patch_name
If need the patch regeneration, in debian/patches prewious already have a 07_orca_desktop_environment.patch named patch file, with implementing the desktop environment announcement feature. Before I generating unified diff file, need fixing only the wrong marked translation message with this patch file, or need both two places fixing the wrong message (debian/patches/07_orca_desktop_environment.patch and already original patch patched src/orca/scripts/default.py file)? What the standard way this situation if a function implementation fix only applied with Ubuntu specific package? I ask this, because prewious I sent patches only upstream level for Orca, this situation when I changing anything with source code, git diff generated prewious proper patches, independent how many source files is changed. Attila -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/744875 Title: [Natty] one desktop environment announce message is wrong marked for translation for src/orca/scripts/default.py file -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
