After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 547853 - Revive MoveOnInfoSave
Revive MoveOnInfoSave
Status: RESOLVED FIXED
Product: banshee
Classification: Other
Component: general
git master
Other Linux
: Normal normal
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
: 550333 (view as bug list)
Depends on:
Blocks: 322877
 
 
Reported: 2008-08-14 23:45 UTC by Ruben Vermeersch
Modified: 2008-09-02 16:45 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Core functionality (7.28 KB, patch)
2008-08-14 23:46 UTC, Ruben Vermeersch 		committed Details | Review
Preference (2.03 KB, patch)
2008-08-14 23:46 UTC, Ruben Vermeersch 		committed Details | Review

Description Ruben Vermeersch 2008-08-14 23:45:03 UTC 
Attached patches re-add the MoveOnInfoSave functionality. This renames files when editing metadata, to keep this information in sync.
Comment 1 Ruben Vermeersch 2008-08-14 23:46:07 UTC 
Created attachment 116621 [details] [review]
Core functionality

This handles the (already in place) MoveOnInfoSave preference.
Comment 2 Ruben Vermeersch 2008-08-14 23:46:45 UTC 
Created attachment 116622 [details] [review]
Preference

Adds a checkbutton to the preferences dialog.
Comment 3 Bertrand Lorentz 2008-08-15 11:35:13 UTC 
I'm wondering if this new preference could be merged with the "Copy files to media folders when importing" one, creating something like "Files follow metadata".

I don't see why you'd want one without the other, but maybe I'm missing something.
Comment 4 Gabriel Burt 2008-08-18 03:42:16 UTC 
Ruben, looks good, go ahead and commit.  I don't want this to languish - we can tweak it later if needed.
Comment 5 Ruben Vermeersch 2008-08-18 09:01:22 UTC 
Committed in r4395 and r4396.
Comment 6 Bertrand Lorentz 2008-09-02 16:45:45 UTC 
*** Bug 550333 has been marked as a duplicate of this bug. ***