Re: [qooxdoo-devel] qooxdoo goes Git/Github

2011-10-28 Thread omrihar
I performed another pull now and it works perfectly! Apparently the branch merge was a real one... Best, Omri -- View this message in context: http://qooxdoo.678.n2.nabble.com/qooxdoo-goes-Git-Github-tp6905496p6939342.html Sent from the qooxdoo mailing list archive at Nabble.com.

Re: [qooxdoo-devel] qooxdoo goes Git/Github

2011-10-28 Thread omrihar
Hi, Congratulations on the move to a DVCS! Being a Mercurial fan myself I decided to try using the extension discussed above [1]. I used the "easy way" installation discussed in [1] (using easy_install) and then cloned the qooxdoo repository directly from github (using hg clone git://github.com/qo

Re: [qooxdoo-devel] qooxdoo goes Git/Github

2011-10-27 Thread thron7
On 10/27/2011 10:20 AM, Phyo Arkar wrote: > i mean mercurial-git extension I've read something about it on passing, which sounded positive. Keep us updated. T. -- The demand for IT networking professionals continues

Re: [qooxdoo-devel] qooxdoo goes Git/Github

2011-10-27 Thread Phyo Arkar
i mean mercurial-git extension On 10/27/11, Phyo Arkar wrote: > Contgrats!! > > I always wanted to see Qooxdoo on Mercurial or Git! > > DCVS are way to go . I love mercurial i hope mercurial-hg extension > will work well with qooxdoo git repo. > > On 10/26/11, thron7 wrote: >> The move to github

Re: [qooxdoo-devel] qooxdoo goes Git/Github

2011-10-27 Thread Phyo Arkar
Contgrats!! I always wanted to see Qooxdoo on Mercurial or Git! DCVS are way to go . I love mercurial i hope mercurial-hg extension will work well with qooxdoo git repo. On 10/26/11, thron7 wrote: > The move to github has been acomplished! > > The qooxdoo repository at http://github.com/qooxdoo

Re: [qooxdoo-devel] qooxdoo goes Git/Github

2011-10-26 Thread thron7
The move to github has been acomplished! The qooxdoo repository at http://github.com/qooxdoo/qooxdoo has been updated from SVN for the last time (rev29012), and will henceforth be the master repo. All commiters have to use git and work against this repo. Users of trunk checkouts will have to ch

Re: [qooxdoo-devel] qooxdoo goes Git/Github

2011-10-25 Thread thron7
Concerns: Commiters only This is just a reminder that we are setting the qooxdoo SVN repo on Sourceforge to read-only tomorrow moring. After that SVN commits to that repo will no longer be possible. If you have any pending commits or local changes that you want to commit through SVN, make sure

Re: [qooxdoo-devel] qooxdoo goes Git/Github

2011-10-21 Thread Burak Arslan
On 10/21/11 15:41, Tobias Oetiker wrote: > Today thron7 wrote: > >> I haven't heard enough about sub-repositories yet. How are they created? >> Can you clone them individually? > the https://github.com/qooxdoo user has multiple sub-repositories > already ... a qooxdoo-contrib user could have that t

Re: [qooxdoo-devel] qooxdoo goes Git/Github

2011-10-21 Thread Tobias Oetiker
Today thron7 wrote: > I haven't heard enough about sub-repositories yet. How are they created? > Can you clone them individually? the https://github.com/qooxdoo user has multiple sub-repositories already ... a qooxdoo-contrib user could have that too ... sounds like a very neat solution to me ...

Re: [qooxdoo-devel] qooxdoo goes Git/Github

2011-10-21 Thread panyasan
thron7-2 wrote: > > > Ah, that would be normal repositories for me. If you are just saying > "create a qooxdoo-contrib account, and host each contrib as its > individual repo in there", then I got it. If you mean something else, > correct me. Sub-repositories must be something else, I heard o

Re: [qooxdoo-devel] qooxdoo goes Git/Github

2011-10-21 Thread thron7
Thanks for the hint, Derrell. T. On 10/21/2011 02:22 PM, Derrell Lipman wrote: On Fri, Oct 21, 2011 at 08:17, thron7 > wrote: Sub-repositories must be something else, I heard of them in relation to what 'svn externals' give you. Yes, there is suc

Re: [qooxdoo-devel] qooxdoo goes Git/Github

2011-10-21 Thread Derrell Lipman
On Fri, Oct 21, 2011 at 08:17, thron7 wrote: Sub-repositories must be something else, I heard of them in > relation to what 'svn externals' give you. Yes, there is such a thing. I have not explored it deeply, but talk with Fabian. They use that facility in Ace. There's some way to mark another

Re: [qooxdoo-devel] qooxdoo goes Git/Github

2011-10-21 Thread thron7
On 10/21/2011 01:23 PM, panyasan wrote: > thron7-2 wrote: >> I haven't heard enough about sub-repositories yet. How are they created? >> Can you clone them individually? >> > Maybe I misunderstood something, but my experience with github is that you > create an account (for example, username "qoo

Re: [qooxdoo-devel] qooxdoo goes Git/Github

2011-10-21 Thread panyasan
thron7-2 wrote: > > I haven't heard enough about sub-repositories yet. How are they created? > Can you clone them individually? > Maybe I misunderstood something, but my experience with github is that you create an account (for example, username "qooxdoo-contrib"), and then create as many repo

Re: [qooxdoo-devel] qooxdoo goes Git/Github

2011-10-21 Thread thron7
On 10/21/2011 09:07 AM, panyasan wrote: > We could have a qooxdoo-contrib account at github and make each contrib a > sub-repository, couldn't we? So they wouldn't be all lumped together. So for > each new contrib, the devs would create a repository and make the author a > committer. Plus, if one

Re: [qooxdoo-devel] qooxdoo goes Git/Github

2011-10-21 Thread thron7
On 10/21/2011 12:11 AM, Greg Hellings wrote: > T. > > On Thu, Oct 20, 2011 at 5:00 PM, thron7 wrote: >> Greg, >> >>> Will the qooxdoo-contrib project be making the same move at some point? >> as I wrote in the weekly, this is open to discussion. But let's assume >> that for a moment, would it re

Re: [qooxdoo-devel] qooxdoo goes Git/Github

2011-10-21 Thread panyasan
We could have a qooxdoo-contrib account at github and make each contrib a sub-repository, couldn't we? So they wouldn't be all lumped together. So for each new contrib, the devs would create a repository and make the author a committer. Plus, if one wants to have a contrib outside under their own a

Re: [qooxdoo-devel] qooxdoo goes Git/Github

2011-10-20 Thread Tobias Oetiker
Today thron7 wrote: Wouldn't you rather have > one repo per contrib? Most people I know only use a few of the 80+ > contribs we have in the repo today. Wouldn't it be easier and more natural > to check them out, follow them, clone them, and create pull requests for > them on a one-repo-per-contrib

Re: [qooxdoo-devel] qooxdoo goes Git/Github

2011-10-20 Thread Tobi Oetiker
On 21.10.2011, at 00:00, "thron7" wrote: > Greg, > >> Will the qooxdoo-contrib project be making the same move at some point? > > as I wrote in the weekly, this is open to discussion. But let's assume > that for a moment, would it really make sense to subsume any number of > contributions in a

Re: [qooxdoo-devel] qooxdoo goes Git/Github

2011-10-20 Thread Greg Hellings
T. On Thu, Oct 20, 2011 at 5:00 PM, thron7 wrote: > Greg, > >> Will the qooxdoo-contrib project be making the same move at some point? > > as I wrote in the weekly, this is open to discussion. But let's assume > that for a moment, would it really make sense to subsume any number of > contribution

Re: [qooxdoo-devel] qooxdoo goes Git/Github

2011-10-20 Thread thron7
Greg, > Will the qooxdoo-contrib project be making the same move at some point? as I wrote in the weekly, this is open to discussion. But let's assume that for a moment, would it really make sense to subsume any number of contributions in a single repository on Github? Wouldn't you rather have on

Re: [qooxdoo-devel] qooxdoo goes Git/Github

2011-10-19 Thread Greg Hellings
Will the qooxdoo-contrib project be making the same move at some point? --Greg On Tue, Oct 18, 2011 at 12:05 PM, thron7 wrote: > About: This only concerns people working with an SVN trunk checkout of > qooxdoo (as opposed to a downloaded SDK). > > Dear trunk users, > > as already announced in th

[qooxdoo-devel] qooxdoo goes Git/Github

2011-10-18 Thread thron7
About: This only concerns people working with an SVN trunk checkout of qooxdoo (as opposed to a downloaded SDK). Dear trunk users, as already announced in the last weekly [1] we will be changing our version control system from SVN to Git. At the same we will be switching the hosting platform f