Make it possible to batch rename all your photos
Submitted by an unknown user
Link to original bug (#716184)
Description
---- Reported by shotwell-maint@gnome.bugs 2010-05-15 11:12:00 -0700 ----
Original Redmine bug id: 1926
Original URL: http://redmine.yorba.org/issues/1926
Searchable id: yorba-bug-1926
Original author: Kostas -
Original description:
In Picasa it is also possible to batch rename all your photos:
[http://picasa.google.com/support/bin/answer.py?hl=en&answer=19548](http://pic asa.google.com/support/bin/answer.py?hl=en&answer=19548)
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:40:00 -0700 ----
History
Comment 1
Updated by Adam Dingle over 3 years ago
-
Priority deleted (
<strike>
_Low_</strike>
)
Comment 2
Updated by Adam Dingle over 2 years ago
- Target version set to 0.9
- Priority set to High
Oops – we didn't notice this patch for a long time! Unfortunately Trac doesn't automatically notify us at the moment when patches are attached (see#2282), so if you do attach a patch it's best to add a comment as well, in which case we will notice.
Looks like this patch is small, so we may yet be able to consider this for 0.9. Jim, please review.
Comment 3
Updated by Adam Dingle over 2 years ago
- Status changed from Open to Review
- Assignee changed from Anonymous to Wolfgang Steitz
Comment 4
Updated by Jim Nelson over 2 years ago
- Status changed from Review to 5
- Resolution set to fixed
- % Done changed from 0 to 100
r2734
Thanks Wolfgang!
Comment 5
Updated by Jim Nelson over 2 years ago
See also #3348 (closed)
Comment 6
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Fixed
--- Bug imported by chaz@yorba.org 2013-11-25 21:44 UTC ---
This bug was previously known as bug 1926 at http://redmine.yorba.org/show_bug.cgi?id=1926 Imported an attachment (id=261660)
Unknown Component Using default product and component set in Parameters Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Version: 0.9
Resolution: RESOLVED FIXED