Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/1527
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user swill commented on the pull request:
https://github.com/apache/cloudstack/pull/1527#issuecomment-216371746
Previous PR was #1374, for book keeping...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your pro
GitHub user milamberspace opened a pull request:
https://github.com/apache/cloudstack/pull/1527
Update L10N resource files with 4.7 strings from Transifex (20160502)
Force "translator" mode with the transifex client.
cc @swill the new PR.
You can merge this pull request int
Github user milamberspace commented on the pull request:
https://github.com/apache/cloudstack/pull/1374#issuecomment-216370438
@swill ok I will do this. But you must understand that the L10N resources
files for each CS version are different and cannot merge together. On the
Transifex
Github user milamberspace closed the pull request at:
https://github.com/apache/cloudstack/pull/1374
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the fea
Github user swill commented on the pull request:
https://github.com/apache/cloudstack/pull/1374#issuecomment-216347252
@milamberspace I think that is probably the best option. Then I will merge
the new one (with these changes) first and forward merge and then merge #1515
and then if
Github user milamberspace commented on the pull request:
https://github.com/apache/cloudstack/pull/1374#issuecomment-216336456
@swill @DaanHoogland Yes, on my local machine, the branch are open against
thr 4.7 branch. The PR in github is against the master, but will be against 4.7.
Github user swill commented on the pull request:
https://github.com/apache/cloudstack/pull/1374#issuecomment-216331189
@DaanHoogland I think this PR should probably be opened against the `4.7`
branch though in order for your point to be valid. Right?
---
If your project is set up f
Github user DaanHoogland commented on the pull request:
https://github.com/apache/cloudstack/pull/1374#issuecomment-216328673
ok, the other way around, but you get what I am warning for.
---
If your project is set up for it, you can reply to this email and have your
reply appear on Gi
Github user swill commented on the pull request:
https://github.com/apache/cloudstack/pull/1374#issuecomment-216327688
@DaanHoogland this is opened against `master` though while #1515 is opened
against `4.8`, so the forward merge of #1515 will affect this one...
---
If your project i
Github user DaanHoogland commented on the pull request:
https://github.com/apache/cloudstack/pull/1374#issuecomment-216324676
@swill I think you want to forward merge before this one and then merge -s
ours or such to prevent this from being merged forward.
4.8 has its own transifex
Github user swill commented on the pull request:
https://github.com/apache/cloudstack/pull/1374#issuecomment-216307729
#1515 is going in today and then we will validate that this one and #1376
don't have merge conflicts once #1515 is in and they will follow right after...
---
If your
Github user rhtyd commented on the pull request:
https://github.com/apache/cloudstack/pull/1374#issuecomment-216306406
Thanks @milamberspace cc @swill @DaanHoogland we need one more LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on Gi
Github user milamberspace commented on the pull request:
https://github.com/apache/cloudstack/pull/1374#issuecomment-216296425
@rhtyd rebase and squash done
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user rhtyd commented on the pull request:
https://github.com/apache/cloudstack/pull/1374#issuecomment-216221597
LGTM, @milamberspace please rebase and squash changes into to a single
commit
tag:easypr
---
If your project is set up for it, you can reply to this email a
Github user milamberspace commented on the pull request:
https://github.com/apache/cloudstack/pull/1374#issuecomment-212325393
@swill I've just rebase from 4.7 update the L10N files and push --force
this PR.
cc @koushik-das
---
If your project is set up for it, you can reply to
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/1374#issuecomment-211860607
@swill Again UI changes related to l10n. I think these can be merged.
---
If your project is set up for it, you can reply to this email and have your
reply appe
Github user bvbharatk commented on the pull request:
https://github.com/apache/cloudstack/pull/1374#issuecomment-198212042
### ACS CI BVT Run
**Sumarry:**
Build Number 109
Hypervisor xenserver
NetworkType Advanced
Passed=106
Failed=12
Skipped=4
GitHub user milamberspace opened a pull request:
https://github.com/apache/cloudstack/pull/1374
Update L10N resource files with 4.7 strings from Transifex (20160127)
cc @remibergsma @bhaisaab @DaanHoogland
You can merge this pull request into a Git repository by running:
$ git
19 matches
Mail list logo
