Re: [Yade-users] [Question #679544]: Best way to fix typos in documentation: source edit + git push?

2019-05-23 Thread Launchpad Janitor
Question #679544 on Yade changed:
https://answers.launchpad.net/yade/+question/679544

Status: Open => Expired

Launchpad Janitor expired the question:
This question was expired because it remained in the 'Open' state
without activity for the last 15 days.

-- 
You received this question notification because your team yade-users is
an answer contact for Yade.

___
Mailing list: https://launchpad.net/~yade-users
Post to : yade-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yade-users
More help   : https://help.launchpad.net/ListHelp


Re: [Yade-users] [Question #679544]: Best way to fix typos in documentation: source edit + git push?

2019-05-07 Thread Gael Lorieul
Question #679544 on Yade changed:
https://answers.launchpad.net/yade/+question/679544

Status: Answered => Open

Gael Lorieul is still having a problem:
Hi all!

On Fri, 3 May 2019 at 23:58, Gael Lorieul
 > First of all, Bruno Chareyre asked me for my GitLab.com user name,
 > [...] So I assume he was considering adding me to the list of team
 > members, possibly with reduced permissions?

El 03-05-19 a las 18:20, Bruno Chareyre escribió:
 > Done, sorry for delay!

El 06-05-19 a las 10:46, Janek Kozicki escribió:
 > Oh good. Now you are part of yade-dev team. Welcome:)
 > You will push to a branch on gitlab and make merge requests.

Awesome, thanks!
I will push something small soon to test all works as it should ;)


El 03-05-19 a las 18:20, Bruno Chareyre escribió:>
 > Please note that you sent reply to yade-users, feel free to use
 > yade-dev for any communication.

I will do so for future conversations, I just wanted to avoid a mess 
where the present conversation would be half in yade-users and half in 
yade-dev ;) .
Now I think the thread has reached to an end (hopefully, if all works as 
expected… XD ), so it does not matter very much anymore.

 > Are you french? Your name sounds so.

I am ;) but living on the other side of the planet for now!

Many thanks for your help!

Gaël

-- 
You received this question notification because your team yade-users is
an answer contact for Yade.

___
Mailing list: https://launchpad.net/~yade-users
Post to : yade-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yade-users
More help   : https://help.launchpad.net/ListHelp


Re: [Yade-users] [Question #679544]: Best way to fix typos in documentation: source edit + git push?

2019-05-06 Thread Janek Kozicki
Question #679544 on Yade changed:
https://answers.launchpad.net/yade/+question/679544

Janek Kozicki posted a new comment:
Solution 2. is for people who prefer to have "group runners" we can
provide that.

-- 
You received this question notification because your team yade-users is
an answer contact for Yade.

___
Mailing list: https://launchpad.net/~yade-users
Post to : yade-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yade-users
More help   : https://help.launchpad.net/ListHelp


Re: [Yade-users] [Question #679544]: Best way to fix typos in documentation: source edit + git push?

2019-05-06 Thread Janek Kozicki
Question #679544 on Yade changed:
https://answers.launchpad.net/yade/+question/679544

Janek Kozicki proposed the following answer:
Oh good. Now you are part of yade-dev team. Welcome :) You will push to
a branch on gitlab and make merge requests.

Along the way you will see what gilab-runners are doing, when you will
click on a 'pipeline' on your first MR.

-- 
You received this question notification because your team yade-users is
an answer contact for Yade.

___
Mailing list: https://launchpad.net/~yade-users
Post to : yade-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yade-users
More help   : https://help.launchpad.net/ListHelp


Re: [Yade-users] [Question #679544]: Best way to fix typos in documentation: source edit + git push?

2019-05-03 Thread Gael Lorieul
Hey Janek,

Thanks for offering your help! :)

El 03-05-19 a las 08:13, Janek Kozicki escribió:> Question #679544 on 
Yade changed:
 > https://answers.launchpad.net/yade/+question/679544
 >
 > Janek Kozicki proposed the following answer:
 >> 2. Merge request from a repository of my own. Requires to have "group
 > runners"
 >
 > I can help with that. Please give me the registration token for your
 > runners. I will add a runner for you. See https://gitlab.com/yade-
 > dev/trunk/merge_requests/112
 >
 > You also need to add a tag "fast" after I add this runner for you.

First of all, Bruno Chareyre asked me for my GitLab.com user name, which 
I shared (`@GLorieul` [1]). So I assume he was considering adding me to 
the list of team members, possibly with reduced permissions?

 From what I understand, solution 2 (i.e. push to repository of your 
own, then merge request to official yade branch) is meant for teams of 
researchers of the same lab who want to work together on a clone of 
Yade, correct?

This is not my case: I am the only person of my team working on granular 
flows, the others are concerned with subjects that are not even related 
to mechanics. So would solution #2 be appropriate in that context?

In practice, I am not familiar with the concept of runners. I could 
learn more about them I guess, but if solution #1 (git push to new 
(temporary) branch of yade) can be worked out, I'd rather do that ;)

Janek, what is your opinion on that?

Gaël

[1]
https://gitlab.com/GLorieul


___
Mailing list: https://launchpad.net/~yade-users
Post to : yade-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yade-users
More help   : https://help.launchpad.net/ListHelp


Re: [Yade-users] [Question #679544]: Best way to fix typos in documentation: source edit + git push?

2019-05-03 Thread Janek Kozicki
Question #679544 on Yade changed:
https://answers.launchpad.net/yade/+question/679544

Janek Kozicki proposed the following answer:
> 2. Merge request from a repository of my own. Requires to have "group
runners"

I can help with that. Please give me the registration token for your
runners. I will add a runner for you. See https://gitlab.com/yade-
dev/trunk/merge_requests/112

You also need to add a tag "fast" after I add this runner for you.

-- 
You received this question notification because your team yade-users is
an answer contact for Yade.

___
Mailing list: https://launchpad.net/~yade-users
Post to : yade-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yade-users
More help   : https://help.launchpad.net/ListHelp


Re: [Yade-users] [Question #679544]: Best way to fix typos in documentation: source edit + git push?

2019-04-29 Thread Gael Lorieul
Hi Bruno,

Bruno Chareyre Mon, 29 Apr 2019 21:53:51 +0200
 > Give me your gitlab.com name. :)

That would be `GLorieul`

Gaël
___
Mailing list: https://launchpad.net/~yade-users
Post to : yade-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yade-users
More help   : https://help.launchpad.net/ListHelp


Re: [Yade-users] [Question #679544]: Best way to fix typos in documentation: source edit + git push?

2019-04-29 Thread Bruno Chareyre
Give me your gitlab.com name. :)
Bruno

Le lun. 29 avr. 2019 16:08, Gael Lorieul  a
écrit :

> Hi Bruno (and the team),
>
> El 26-04-19 a las 10:03, Bruno Chareyre escribió:
> > Yes you can write emails to yade-dev.
>
> Ok, I'll do that next time ;)
> But I'll finish the present conversation in yade-users to keep it simple
> (and avoid possibly a mess).
>
> > It would be very helpful if you could try method [1] (gitlab),
> especially if you plan to change more later,  and it should not be a big
> deal.
> > Assuming you are working on source code pulled from the gitlab
> repository (else send use the result of "git remote -v"):
> >
> > cd trunk
> > git status #list which files you have modified
> > git commit file1 file2 file3 #the files you changed
> > git pull --rebase
> > git push origin master:fixtypo
>
> I tried that last Friday and got: (same thing today…)
>
>  > GitLab: You are not allowed to push code to this project.
>  fatal: Could not read from remote repository.
>
>  Please make sure you have the correct access rights and the
> repository exists.
>
> Some info about my `origin` repository i.e. `git remote show origin`
>
>  remote origin
>  Fetch URL: g...@gitlab.com:yade-dev/trunk.git
>  Push URL: g...@gitlab.com:yade-dev/trunk.git
>  Branch HEAD: master
>  Remote branch:
>  master  tracked
>
> I am using SSH authentication, and the gitlab server has the
> corresponding public key (I checked which key I am using with `ssh -vT
> g...@gitlab.com`).
>
> Https authentication also fails (and I checked the credentials I use):
>
>  Username for 'https://gitlab.com': g* dot l* at coandev dot com
>  Password for 'https://*@gitlab.com':
>  remote: You are not allowed to push code to this project.
>
> Although I cannot push, I can pull i.e. `git pull --rebase` succeeds.
>
> In the GitLab web interface I can see that I am *not* a member of the
> `yade-dev/trunk` project (my user name is g* dot l* at coandev dot com
> i.e. same as the e-mail address I am using but with a different host)
>
> Could that be that I would need to be a member of the `yade-dev/trunk`
> project for approach #1 to succeed? Any ideas? ;)
>
> Gaël
>
>
> PS:
> Result of `git remote -v`
>
>  origin g...@gitlab.com:yade-dev/trunk.git (fetch)
>  origin g...@gitlab.com:yade-dev/trunk.git (push)
>  origin_https   https://gitlab.com/yade-dev/trunk.git (fetch)
>  origin_https   https://gitlab.com/yade-dev/trunk.git (push)
>
> Note: remote `origin` is the upstream.
> ___
> Mailing list: https://launchpad.net/~yade-users
> Post to : yade-users@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~yade-users
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~yade-users
Post to : yade-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yade-users
More help   : https://help.launchpad.net/ListHelp


Re: [Yade-users] [Question #679544]: Best way to fix typos in documentation: source edit + git push?

2019-04-29 Thread Gael Lorieul
Hi Bruno (and the team),

El 26-04-19 a las 10:03, Bruno Chareyre escribió:
> Yes you can write emails to yade-dev.

Ok, I'll do that next time ;)
But I'll finish the present conversation in yade-users to keep it simple 
(and avoid possibly a mess).

> It would be very helpful if you could try method [1] (gitlab), especially if 
> you plan to change more later,  and it should not be a big deal.
> Assuming you are working on source code pulled from the gitlab repository 
> (else send use the result of "git remote -v"):
> 
> cd trunk
> git status #list which files you have modified
> git commit file1 file2 file3 #the files you changed
> git pull --rebase
> git push origin master:fixtypo

I tried that last Friday and got: (same thing today…)

 > GitLab: You are not allowed to push code to this project.
 fatal: Could not read from remote repository.

 Please make sure you have the correct access rights and the 
repository exists.

Some info about my `origin` repository i.e. `git remote show origin`

 remote origin
 Fetch URL: g...@gitlab.com:yade-dev/trunk.git
 Push URL: g...@gitlab.com:yade-dev/trunk.git
 Branch HEAD: master
 Remote branch:
 master  tracked

I am using SSH authentication, and the gitlab server has the 
corresponding public key (I checked which key I am using with `ssh -vT 
g...@gitlab.com`).

Https authentication also fails (and I checked the credentials I use):

 Username for 'https://gitlab.com': g* dot l* at coandev dot com
 Password for 'https://*@gitlab.com':
 remote: You are not allowed to push code to this project.

Although I cannot push, I can pull i.e. `git pull --rebase` succeeds.

In the GitLab web interface I can see that I am *not* a member of the 
`yade-dev/trunk` project (my user name is g* dot l* at coandev dot com 
i.e. same as the e-mail address I am using but with a different host)

Could that be that I would need to be a member of the `yade-dev/trunk` 
project for approach #1 to succeed? Any ideas? ;)

Gaël


PS:
Result of `git remote -v`

 origin g...@gitlab.com:yade-dev/trunk.git (fetch)
 origin g...@gitlab.com:yade-dev/trunk.git (push)
 origin_https   https://gitlab.com/yade-dev/trunk.git (fetch)
 origin_https   https://gitlab.com/yade-dev/trunk.git (push)

Note: remote `origin` is the upstream.
___
Mailing list: https://launchpad.net/~yade-users
Post to : yade-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yade-users
More help   : https://help.launchpad.net/ListHelp


Re: [Yade-users] [Question #679544]: Best way to fix typos in documentation: source edit + git push?

2019-04-26 Thread Bruno Chareyre
Question #679544 on Yade changed:
https://answers.launchpad.net/yade/+question/679544

Status: Open => Answered

Bruno Chareyre proposed the following answer:
Hi Gaël,
Thanks vey much for contributing.
Yes you can write emails to yade-dev.
It would be very helpful if you could try method [1] (gitlab), especially if 
you plan to change more later,  and it should not be a big deal.
Assuming you are working on source code pulled from the gitlab repository (else 
send use the result of "git remote -v"):

cd trunk
git status #list which files you have modified
git commit file1 file2 file3 #the files you changed
git pull --rebase
git push origin master:fixtypo

Here "fixtypo" is the name of the new branch that will be created.

Bruno

-- 
You received this question notification because your team yade-users is
an answer contact for Yade.

___
Mailing list: https://launchpad.net/~yade-users
Post to : yade-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yade-users
More help   : https://help.launchpad.net/ListHelp


Re: [Yade-users] [Question #679544]: Best way to fix typos in documentation: source edit + git push?

2019-04-25 Thread Gael Lorieul
Question #679544 on Yade changed:
https://answers.launchpad.net/yade/+question/679544

Status: Answered => Open

Gael Lorieul is still having a problem:
Hi,

At last I am submitting the typo fixes in the documentation that I 
promised some time ago already…  Following the documentation [1], I am 
sending it as a patch file attached to the present e-mail. [2]

It's not much, but hopefully it's just a start 

Cheers,

Gaël

PS: perhaps I should be using the yade-dev mailing for such 
communication? If so I assume all I have to do is send an e-mail to the 
list? Unlike the yade-users mailing list where it is required to ask 
questions from the Launchpad interface?

[1]
https://yade-dev.gitlab.io/trunk/github.html#pushing-changes-to-remote-repository

[2]
The documentation presents three methods:
  1. Merge request from new branch in Yade repository. Requires me to be 
a member, which I am not.
  2. Merge request from a repository of my own. Requires to have "group 
runners", which I don't think I have. Also GitLab does not allow me to 
create a merge request to `yade-dev/trunk` from either the 
`yade-dev/trunk` page (no "Add merge request" item in the "+" menu), nor 
from the "+" menu of my own branch (which does have an "Add merge 
request" item, but does not let me select "yade-dev/trunk" as destination.
  3. Send git patch by e-mail: that's what I am doing 

-- 
You received this question notification because your team yade-users is
an answer contact for Yade.

___
Mailing list: https://launchpad.net/~yade-users
Post to : yade-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yade-users
More help   : https://help.launchpad.net/ListHelp


Re: [Yade-users] [Question #679544]: Best way to fix typos in documentation: source edit + git push?

2019-03-26 Thread Robert Caulk
Question #679544 on Yade changed:
https://answers.launchpad.net/yade/+question/679544

Status: Open => Answered

Robert Caulk proposed the following answer:
Yes, absolutely :-). Yade recently migrated to gitlab where developers
push to branches and then "merge request" those branches into Yade.
Other developers review the merge request and then accept it if it looks
OK. Details of how to do this can be found here [1].

[1]https://yade-dev.gitlab.io/trunk/github.html#pushing-changes-to-
remote-repository

-- 
You received this question notification because your team yade-users is
an answer contact for Yade.

___
Mailing list: https://launchpad.net/~yade-users
Post to : yade-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yade-users
More help   : https://help.launchpad.net/ListHelp


[Yade-users] [Question #679544]: Best way to fix typos in documentation: source edit + git push?

2019-03-25 Thread Gael Lorieul
New question #679544 on Yade:
https://answers.launchpad.net/yade/+question/679544

Hi all!

I've found a few typos by reading the doc: what is the best way to fix them? 
Would it be ok if I fix them myself in the source code and git push it? (let's 
say that it could be a first baby step in contributing to Yade)

Thanks for putting together this great piece of software! ;)

Gaël


-- 
You received this question notification because your team yade-users is
an answer contact for Yade.

___
Mailing list: https://launchpad.net/~yade-users
Post to : yade-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yade-users
More help   : https://help.launchpad.net/ListHelp