← Back to branch summary

~nskaggs/+junk/ubuntu-community-accomplishments

« back to all changes in this revision

Viewing changes to generated/po/da.po

 * Updating translations.

Show diffs side-by-side

added added

removed removed

Lines of Context:
generated/po/da.po
7
7
msgstr ""
8
8
"Project-Id-Version: ubuntu-community-accomplishments\n"
9
9
"Report-Msgid-Bugs-To: FULL NAME <EMAIL@ADDRESS>\n"
10
 
"POT-Creation-Date: 2012-04-26 18:06-0700\n"
 
10
"POT-Creation-Date: 2012-04-26 22:23-0700\n"
11
11
"PO-Revision-Date: 2012-04-08 17:49+0000\n"
12
12
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
13
13
"Language-Team: Danish <da@li.org>\n"
14
14
"MIME-Version: 1.0\n"
15
15
"Content-Type: text/plain; charset=UTF-8\n"
16
16
"Content-Transfer-Encoding: 8bit\n"
17
 
"X-Launchpad-Export-Date: 2012-04-28 05:19+0000\n"
 
17
"X-Launchpad-Export-Date: 2012-04-29 05:23+0000\n"
18
18
"X-Generator: Launchpad (build 15149)\n"
19
19
 
20
20
#. ACCOMPLISHMENT: LoCo Team Member ('title' field)
245
245
#. ACCOMPLISHMENT: First Bazaar Branch Merged ('steps' field)
246
246
#. .
247
247
#. ENGLISH TRANSLATION:
248
 
#. You first need to perform a <i>Merge Proposal</i> to propose your branch is merged into another one. Go to the Launchpad page for the branch that you uploaded and you should see a Propose XXXXXXXXXX
 
248
#. You first need to perform a <i>Merge Proposal</i> to propose your branch is merged into another one. Go to the Launchpad page for the branch that you uploaded and you should see a <i>Propose For Merging</i> link. Click it.
 
249
#. In the form choose the branch you want to merge into and fill a detailed description of the change, fix, or feature that you have contributed.
 
250
#. Click the <i>Propose Merge</i> button to submit your contribution.
249
251
#. Wait for one of the target branch's reviewers to review your code, they will either (1) accept your code, and it will be merged, (2) modify your code slightly, and then merge it, or (3) ask for you to make some improvements before they merge it.
250
252
#. If they request changes to be made, make the changes requested and push them into your branch. Then comment back on your proposal to say that you have made the requested changes.
251
253
#. Now wait for the developer to review your changes. When it is merged you will get an email to inform you it was merged in.
254
256
#. Add a series of step-by-step instructions for how to accomplish this trophy.
255
257
#. NOTE: Put each step on a new line
256
258
#. FORMATTING ALLOWED: <i> <strong> <tt>
257
 
#: ../accomplishments/first-branch-merged.c:48
 
259
#: ../accomplishments/first-branch-merged.c:50
258
260
msgid "first-branch-merged_steps"
259
261
msgstr ""
260
262
 
270
272
#. Add tips and best practise for accomplishing this trophy.
271
273
#. NOTE: Put each tip on a new line
272
274
#. FORMATTING ALLOWED: <i> <strong> <tt>
273
 
#: ../accomplishments/first-branch-merged.c:62
 
275
#: ../accomplishments/first-branch-merged.c:64
274
276
msgid "first-branch-merged_tips"
275
277
msgstr ""
276
278
 
283
285
#. Add things the user should not do when working to accomplish this trophy.
284
286
#. NOTE: Put each pitfall on a new line
285
287
#. FORMATTING ALLOWED: <i> <strong> <tt>
286
 
#: ../accomplishments/first-branch-merged.c:73
 
288
#: ../accomplishments/first-branch-merged.c:75
287
289
msgid "first-branch-merged_pitfalls"
288
290
msgstr ""
289
291
 
296
298
#. ----- TRANSLATION INSTRUCTIONS -----
297
299
#. Add related web addresses (don't include a HTML link).
298
300
#. NOTE: Put each URL on a new line
299
 
#: ../accomplishments/first-branch-merged.c:84
 
301
#: ../accomplishments/first-branch-merged.c:86
300
302
msgid "first-branch-merged_links"
301
303
msgstr ""
302
304
 
309
311
#. Add related help resources (e.g. IRC channel names).
310
312
#. NOTE: Put each help resource on a new line
311
313
#. FORMATTING ALLOWED: <i> <strong> <tt>
312
 
#: ../accomplishments/first-branch-merged.c:95
 
314
#: ../accomplishments/first-branch-merged.c:97
313
315
msgid "first-branch-merged_help"
314
316
msgstr ""
315
317