[strings] logged into vs. logged in to
Submitted by Adam Dingle
Link to original bug (#715971)
Description
---- Reported by adam@yorba.org 2010-03-14 09:37:00 -0700 ----
Original Redmine bug id: 1564
Original URL: http://redmine.yorba.org/issues/1564
Searchable id: yorba-bug-1564
Original author: Adam Dingle
Original description:
A grammar nit: For Shotwell 0.5, we had to decide whether to use the spelling “logged into†or “logged in to†in our publishing dialogs. A few of us had a brief discussion and chose “logged intoâ€. Allison has registered her dissent here:
!http://absonance.blogspot.com/2010/03/into-vs-in-to.html
Now that we have the luxury of time, we can think about this more for 0.6.
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:46:00 -0700 ----
History
Comment 1
Updated by Adam Dingle over 3 years ago
- Subject changed from logged into vs. logged in to to [strings] logged into vs. logged in to
Comment 2
Updated by Adam Dingle over 3 years ago
- Subject changed from [strings] logged into vs. logged in to to logged into vs. logged in to
Comment 3
Updated by Adam Dingle over 3 years ago
- Subject changed from logged into vs. logged in to to [strings] logged into vs. logged in to
Comment 4
Updated by Adam Dingle over 3 years ago
- Subject changed from [strings] logged into vs. logged in to to logged into vs. logged in to
Comment 5
Updated by Adam Dingle over 3 years ago
-
Priority deleted (
<strike>
_High_</strike>
)
Comment 6
Updated by Adam Dingle over 3 years ago
- Priority set to High
Comment 7
Updated by Adam Dingle over 3 years ago
- Subject changed from logged into vs. logged in to to [strings] logged into vs. logged in to
Comment 8
Updated by Adam Dingle over 3 years ago
- Status changed from Open to 5
- Resolution set to wontfix
- % Done set to 0
Comment 9
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Invalid
--- Bug imported by chaz@yorba.org 2013-11-25 21:43 UTC ---
This bug was previously known as bug 1564 at http://redmine.yorba.org/show_bug.cgi?id=1564
Unknown Component Using default product and component set in Parameters Unknown version " in product shotwell. Setting version to "!unspecified". 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.
Resolution: RESOLVED INVALID