Merge lp:~om26er/ubuntu/maverick/nautilus/nautilus-fix-630512-maverick into lp:ubuntu/maverick-proposed/nautilus
Proposed by
Omer Akram
Status: | Merged |
---|---|
Merge reported by: | Sebastien Bacher |
Merged at revision: | not available |
Proposed branch: | lp:~om26er/ubuntu/maverick/nautilus/nautilus-fix-630512-maverick |
Merge into: | lp:ubuntu/maverick-proposed/nautilus |
Diff against target: |
56 lines (+35/-1) 3 files modified
debian/changelog (+7/-0) debian/patches/100_dont_treat_tilda_as_a_relative_path.patch (+27/-0) debian/patches/series (+1/-1) |
To merge this branch: | bzr merge lp:~om26er/ubuntu/maverick/nautilus/nautilus-fix-630512-maverick |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Artur Rona (community) | Approve | ||
Bilal Akhtar (community) | Needs Fixing | ||
Ubuntu Sponsors | Pending | ||
Review via email: mp+45048@code.launchpad.net |
Description of the change
cherry picked from upstream git to fix bug 630512. although the issue is a very small one but it got media attention and is a regression-release
To post a comment you must log in.
Looks good, except for a few not-so-important problems with your patch:
1) Change the Origin: DEP-3 tag in debian/ patches/ dont_treat_ tilda_as_ a_relative_ path.patch to Applied-Upstream:
2) In the changelog, (LP: 630512) is not likely to close the bug. Make it (LP: #630512).
3) I may be wrong, but the usual convention is to get the new patch apply the last in debian/ patches/ series. Moreover, the proper convention is to have a number at the beginning of the name of the patch, so in this case rename the patch to 100_dont_ treat_tilda_ as_a_relative_ path.patch and make the same change in debian/ patches/ series as well.