GNU nano - Patches: patch #7025, Patch to fix launchpad bug 471568
You are not allowed to post comments on this tracker with your current authentication level.
patch #7025: Patch to fix launchpad bug 471568
Submitter: | Brian Szymanski <skibrianski> | ||
Submitted: | Mon 14 Dec 2009 04:26:52 AM UTC | ||
Priority: | 5 - Normal | Status: | Done |
Privacy: | Public | Assigned to: | astyanax |
Open/Closed: | Closed | Release: | None |
Tue 05 Jan 2010 10:01:04 PM UTC, comment #3: |
Brian Szymanski <skibrianski> |
Sun 20 Dec 2009 05:51:32 AM UTC, comment #2: I forgot to say thank you. Thank you for this patch, it looks great :) |
Chris Allegretta <astyanax> |
Sun 20 Dec 2009 05:50:17 AM UTC, comment #1: Applied and credited in svn r4467, and will be in nano 2.2.2. If Ubuntu is not interested in going to 2.2 anytime soon, I can eventually make a new 2.0 release. |
Chris Allegretta <astyanax> |
Mon 14 Dec 2009 04:26:52 AM UTC, original submission:
I've fixed a crash at save time when "set backup" is enabled and the user does not save to the default file location. The bug is not ubuntu specific, but I reported it there first:
|
Brian Szymanski <skibrianski> |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 5 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2014-02-22 | bens | Open/Closed | Open | Closed | |
2009-12-20 | astyanax | Status | None | Done | |
Assigned to | None | astyanax | |||
2009-12-14 | skibrianski | Attached File | - | Added launchpad-471568.patch, #19256 | |
Carbon-Copy | - | Added skibrianski |
Powered by Savane 3.13-d3ae.
Corresponding source code
I think a new 2.0.x release would be appropriate, given how this bug is a "only needs to burn you once" kind of thing... The next ubuntu release is going to nano 2.2, but that leaves all the other supported ubuntu releases subject to this bug (not to mention other distros, OSes, etc). Presumably everybody having their own patches against the same bug is a Bad Thing, yea?