Conversation

Notices

1. MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Saturday, 07-Mar-2015 13:24:04 UTC MMN-o ✅⃠

   • digital dreamer
   Yes, that should be possible! Don't worry. But feel free to keep reminding me ;)
   • MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Saturday, 07-Mar-2015 17:56:59 UTC MMN-o ✅⃠

     • digital dreamer
     I think we should reasonably not track the *.mo files in git though. (however, if we release a tarball they should of course be pre-compiled)
   • MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Saturday, 07-Mar-2015 18:49:47 UTC MMN-o ✅⃠

     • digital dreamer
     Thanks, I'll merge it when you have only the .po files. (please don't just add a commit that deletes the files, since there's no point in adding 10 MiB of .mo files to history just to delete them directly afterwards :P)
   • MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Saturday, 07-Mar-2015 19:36:53 UTC MMN-o ✅⃠

     • digital dreamer
     You can just reset to before the commit and do git push -f to overwrite the currently uploaded merge branch. But do whatever you feel comfortable with.
   • MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Sunday, 08-Mar-2015 10:04:33 UTC MMN-o ✅⃠

     • digital dreamer
     @digitaldreamer If you look at the merge request page there is a little question mark, clicking it informs you how to specifically update the merge request (and not just your repo's branch): https://gitorious.org/social/mainline/merge_requests/56
   • MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Sunday, 08-Mar-2015 10:30:23 UTC MMN-o ✅⃠

     • digital dreamer
     • gstranslate
     Thanks, you rock! :) I'll hopefully get it done before this day is over (CET). !gstranslate