I will contribute soon again. But I don't really care if it is on CVS or GitHub. I just wanted to be sure to address the correct repository.
(woah: You cannot make another post so soon after your last. :( Sorry for writing that fast :D)
Board index ‹ Announcements ‹ Moving to GitHub.com: Call for developers - CVS/SVN affected
20 posts
• Page 2 of 2 • 1, 2
Re: Moving to GitHub.com: Call for developers - CVS/SVN affeI will contribute soon again. But I don't really care if it is on CVS or GitHub. I just wanted to be sure to address the correct repository.
(woah: You cannot make another post so soon after your last. :( Sorry for writing that fast :D)
Re: Moving to GitHub.com: Call for developers - CVS/SVN affeHi!
Spartacus now lives on github: http://blog.s9y.org/archives/237-Sparta ... -read.html (and fornicates to CVS) Regards, Garvin # Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/ # or use my PayPal account "paypal {at} supergarv (dot) de" # My "other" hobby: http://flickr.garv.in/
Re: Moving to GitHub.com: Call for developers - CVS/SVN affe
Yay! (Let's hope it doesn't catch anything ugly along the way.) YL
Re: Moving to GitHub.com: Call for developers - CVS/SVN affeI like this news ;)
I'd like to track a branch which will make my rapid deployment with chef much easier.... is it considered safe to track the (for example) 1.6 branch? I assume all new features will go to master (or a new branch)? and only bug fixes to the current releases branch? or are there no such guarantees? Thanks! -
Re: Moving to GitHub.com: Call for developers - CVS/SVN affe
That's the way it's planned – master is the "bleeding edge", 1.6 will be used for all 1.6.x versions to come. YL
20 posts
• Page 2 of 2 • 1, 2
Who is onlineUsers browsing this forum: No registered users and 3 guests |