Re: [VOTE][LAZY] Migrate Commons SCXML to Git

2015-07-08 Thread Benedikt Ritter
Hello Woonson, one think you will have to do after the migration is to create a ticket for the github mirror. Otherwise it will continue mirroring the SVN repo. Benedikt 2015-07-09 6:06 GMT+02:00 Woonsan Ko : > Thanks for your support, Ate! :-) > > It was already migrated to git (INFRA-9952). I

Re: [VOTE][LAZY] Migrate Commons SCXML to Git

2015-07-08 Thread Woonsan Ko
Thanks for your support, Ate! :-) It was already migrated to git (INFRA-9952). I commented about my validations there. Everything seems very fine. I will announce it to user/dev community once it gets fully available. Cheers, Woonsan On Wed, Jul 8, 2015 at 7:26 PM, Ate Douma wrote: > Sorry for

Re: [VOTE][LAZY] Migrate Commons SCXML to Git

2015-07-08 Thread Ate Douma
Sorry for the too late response, but I would have voted +1 too :) Ate On 2015-07-08 20:27, Woonsan Ko wrote: Apache Commons Developers, This VOTE has passed with the following votes: +1 Dave Brosius +1 James Carman (PMC) +1 Gary Gregory (PMC) +1 Woonsan Ko Thank you all f

Re: [RESULT] [VOTE][LAZY] Migrate Commons SCXML to Git

2015-07-08 Thread Woonsan Ko
You can monitor the progress with this INFRA issue: - https://issues.apache.org/jira/browse/INFRA-9952 Thanks, Woonsan On Wed, Jul 8, 2015 at 2:31 PM, Woonsan Ko wrote: > Apache Commons Developers, > > This VOTE has passed with the following votes: > > +1 Dave Brosius > +1 James Carman

[RESULT] [VOTE][LAZY] Migrate Commons SCXML to Git

2015-07-08 Thread Woonsan Ko
Apache Commons Developers, This VOTE has passed with the following votes: +1 Dave Brosius +1 James Carman (PMC) +1 Gary Gregory (PMC) +1 Woonsan Ko Thank you all for voting! I will create an INFRA ticket soon and keep you updated about the progress and availabilities. Regards,

Re: [VOTE][LAZY] Migrate Commons SCXML to Git

2015-07-08 Thread Woonsan Ko
Apache Commons Developers, This VOTE has passed with the following votes: +1 Dave Brosius +1 James Carman (PMC) +1 Gary Gregory (PMC) +1 Woonsan Ko Thank you all for voting! I will create an INFRA ticket soon and keep you updated about the progress and availabilities. Regards,

Re: [Math] Git misc (backport)

2015-07-08 Thread James Carman
Git can merge through file moves too. On Wed, Jul 8, 2015 at 12:28 PM Phil Steitz wrote: > On 7/8/15 9:00 AM, James Ring wrote: > > You should be able to see all the branches with git branch -a. You can > > check them out to work on them, e.g. git checkout -b MATH_3_X > > remotes/origin/MATH_3_X

Re: [Math] Git misc (backport)

2015-07-08 Thread Phil Steitz
On 7/8/15 9:00 AM, James Ring wrote: > You should be able to see all the branches with git branch -a. You can > check them out to work on them, e.g. git checkout -b MATH_3_X > remotes/origin/MATH_3_X > > How do you want to backport? Are you looking to cherry-pick individual > changes from the maste

Re: [Math] Git misc (backport)

2015-07-08 Thread James Ring
You should be able to see all the branches with git branch -a. You can check them out to work on them, e.g. git checkout -b MATH_3_X remotes/origin/MATH_3_X How do you want to backport? Are you looking to cherry-pick individual changes from the master branch back into 3_X? After you've checked out

Re: [Math] Git misc (backport)

2015-07-08 Thread Gilles
On Wed, 08 Jul 2015 12:22:03 +, James Carman wrote: Try merging first On Wed, Jul 8, 2015 at 7:27 AM Gilles wrote: Hmm. What I need is a recipe from step _zero_: $ git remote -v show origin https://git-wip-us.apache.org/repos/asf/commons-math.git (fetch) origin https://git-wip-us.ap

Re: [Math] Git misc (backport)

2015-07-08 Thread James Carman
Try merging first On Wed, Jul 8, 2015 at 7:27 AM Gilles wrote: > Hi. > > What is the easiest/fastest/safest way to backport changes to > the 3.x branch? > > Wouldn't it be a good idea to add some info about what other > branches exist into the "doc" directory (together with the > answer to the ab

[Math] Git misc (backport)

2015-07-08 Thread Gilles
Hi. What is the easiest/fastest/safest way to backport changes to the 3.x branch? Wouldn't it be a good idea to add some info about what other branches exist into the "doc" directory (together with the answer to the above question)? Thanks, Gilles