Nao

  • Dadman with a boy
  • Posts: 16,021
Re: Language revs
« Reply #120,  »
I'm absolutely for any new translations.

What I'm against, however, is wasting time. So, if you want your translations to be in the main languages repo, you should learn how to handle Github and pull requests. That's all.
Yesterday you sent empty pull requests. Today you sent one pull request *per* file, meaning I got an e-mail notification for each of those. When I started accepting the pull requests, I then realized the files were all committed to the root folder (which is NOT for anything other than English files, this isn't SMF, this is Wedge, where files are carefully sorted in language folders!) So I had to do another commit to put them all into place. You also committed a junk file in the lot. It's a real mess. So I said, I'll stop merging your PRs, yet you kept sending them so at the end I just canceled them all.

All I want is a clean repo with just a single commit for all of your files. That's all... Just create a new repo locally from Github, move your new files to the dutch folder, right-click them all, "Add", then commit, and send a single pull request (you can do that one from the Github website as long as it knows your repo is forked from mine, IIRC). It's really easy... It just takes a couple of minutes. Not the couple of hours it took you to upload everything manually...

CerealGuy

  • Posts: 343
Re: Language revs
« Reply #121,  »
@Freñiçh  If you need help with git, feel free to ask. Git has a steep learning curve but is absolutly worth learning it.

Nao

  • Dadman with a boy
  • Posts: 16,021
Re: Language revs
« Reply #122,  »
I'm not trying to frustrate anyone. Just trying to frustrate *me* as little as possible. :P

Freñiçh

  • Webmaster Linux Mint Forum
  • All i want is a couple days off
  • Posts: 131
Re: Language revs
« Reply #123,  »
Quote from Nao on April 17th, 05:21 PM
I'm absolutely for any new translations.

All I want is a clean repo with just a single commit for all of your files. That's all... Just create a new repo locally from Github, move your new files to the dutch folder, right-click them all, "Add", then commit, and send a single pull request (you can do that one from the Github website as long as it knows your repo is forked from mine, IIRC). It's really easy... It just takes a couple of minutes. Not the couple of hours it took you to upload everything manually...
Well i am sorry it was not my intention to cause you so much trouble,but i can't upload files directly into language/Dutch because file uploads require push access to your repository.

So i compare base fork with the head fork,and drag the remaining files into my repository.(Github is what concerns to me a struggle but i am trying to understand the logic behind it )

Create a new branch for this commit and start a pull request named remaining dutch language files.
4 commits are still open (just don't now how to deleted the first 3 commits),but the last one ¨Upload remaining files¨ remains all the not yet added dutch language files.

Nao

  • Dadman with a boy
  • Posts: 16,021
Re: Language revs
« Reply #124,  »
[Commit revision cf3ba32]
Author: French77
Date: Tue, 18 Apr 2017 23:57:28 +0200
Stats: 22 files changed; +3417 (insertions), -0 (deletion)

  • remaining dutch language files (#75)
  • ManageScheduledtasks.dutch.php
  • Upload remaining files
  • Dutch language
Re: Language revs
« Reply #125,  »
[Commit revision db90bfd]
Author: Nao
Date: Tue, 18 Apr 2017 23:59:26 +0200
Stats: 2 files changed; +0 (insertion), -179 (deletions)

  • Nearly there! ;) (ManageScheduledtasks.dutch.php, dutch/license.txt)
Re: Language revs
« Reply #126,  »
I also merged your topic-solved commits.
Quote from Freñiçh on April 18th, 07:40 PM
Well i am sorry it was not my intention to cause you so much trouble,but i can't upload files directly into language/Dutch because file uploads require push access to your repository.
Well, obviously that's the pull request system. (?)
Quote
So i compare base fork with the head fork,and drag the remaining files into my repository.(Github is what concerns to me a struggle but i am trying to understand the logic behind it )
Yeah, it's quite a bit painful, I had to go through that too, but multiply by 1000 because I also had to rebase stuff, rewrite tons of commits through the command line... It took me weeks of work, just to get it to what it is now. :^^;: